-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash: NSFetchedResultsController + NSObjectInaccessibleException #436
Comments
GCD Queue: Main
GCD Queue: com.simperium.processor.Notification
Note: This stack trace was produced by WPiOS 4.6.1 + Simperium Mark 0.7.2 |
This was referenced Jan 26, 2015
jleandroperez
added a commit
that referenced
this issue
Jan 28, 2015
Fixes NSObjectInaccessibleException
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Scenario:
resultsController performFetch:
inner workings, objects are initially loaded as faults.Results:
There is a (really hard to trigger) race condition between steps (1) and (3), in which the objects what were loaded as faults are no longer relevant.
Problem in this scenario is that the NSFetchedResultsController instance is locking the main thread, and thus, preventing the NSManagedObjectContextDidSaveNotification from getting merged. Which, in turn, causes invalid objects to be accessed.
Notes:
This is a side effect of not using NSManagedObjectContext's parenting mechanism, which has been removed due to a Core Data Deadlock (Reference Issue #376).
The text was updated successfully, but these errors were encountered: