EXC_BREAKPOINT on NSFetchedResultsController.performFetch() because of -[CFString isNSString__]: message sent to deallocated instance

By -

I'm running into a repeatable crash when calling -performFetch on my NSFetchedResultsController in what SEEMS like a data-related crash:

 NSFetchedResultsController *aFetchedResultsController =
        [[NSFetchedResultsController alloc] initWithFetchRequest:fetchRequest
                                            managedObjectContext:self.managedObjectContext
                                              sectionNameKeyPath:sectionnamekeypath
                                                       cacheName:cacheName];
        

aFetchedResultsController.delegate = self;

NSError *error = nil;
if (NO == [aFetchedResultsController performFetch:&error]) {
    NSLog(@"Unresolved error %@, %@", error, [error userInfo]);
}

It crashes at the performFetch() call. I turned on Zombie checking and it printed:

*** -[CFString isNSString__]: message sent to deallocated instance 0x12c6071d0

I've checked all of the strings in my function and I can't find a string that has that address. I NSLog()'d all of the strings along with their address locations. I figured it would break on whatever NSLog() line that referenced the string in question, but all of them were still valid.

This makes me think this is a problem inside NSFetchedResultsController.performFetch() but it's hard to imagine that they have this kind of bug. So, what else can I do to find out what string this is?

I haven't run into problems like this since we switched over to ARC. I'm not sure how to figure out where this string comes from.

It SEEMS like this is data related though. My app pulls down data from our server, imports it into Core Data, and then uses the NSFetchedResultsController to show the data in a UITableView. I can login as various different users, download their data, and the FRC fetches and works just fine. But when I login as this one particular user, then it crashes. That user is one of our biggest users and their dataset is thousands and thousands of records, so it's not something I can easily look through to visually find things that might be weird. Doing further testing and will update this if I find any new info.

Any help?



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more