ios – EXC_BREAKPOINT on NSFetchedResultsController.performFetch() due to -[CFString isNSString__]: message despatched to deallocated occasion


I am working right into a repeatable crash when calling -performFetch on my NSFetchedResultsController in what SEEMS like a data-related crash:

 NSFetchedResultsController *aFetchedResultsController =
        [[NSFetchedResultsController alloc] initWithFetchRequest:fetchRequest

aFetchedResultsController.delegate = self;

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

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

*** -[CFString isNSString__]: message despatched to deallocated occasion 0x12c6071d0

I’ve checked all the strings in my operate and I can not discover a string that has that deal with. I NSLog()’d all the strings together with their deal with areas. I figured it might break on no matter NSLog() line that referenced the string in query, however all of them had been nonetheless legitimate.

This makes me suppose it is a downside inside NSFetchedResultsController.performFetch() nevertheless it’s onerous to think about that they’ve this sort of bug. So, what else can I do to seek out out what string that is?

I have never run into issues like this since we converted to ARC. I am unsure how to determine the place this string comes from.

It SEEMS like that is information associated although. My app pulls down information from our server, imports it into Core Knowledge, after which makes use of the NSFetchedResultsController to indicate the information in a UITableView. I can login as varied completely different customers, obtain their information, and the FRC fetches and works simply superb. However once I login as this one specific person, then it crashes. That person is one in all our greatest customers and their dataset is hundreds and hundreds of data, so it isn’t one thing I can simply look by way of to visually discover issues that is perhaps bizarre. Doing additional testing and can replace this if I discover any new information.

Any assist?


Leave a Reply