Databases
StackOverflow2013
Postsdbo
PODeadlock using AFIncrementalStore and NSFetchedResultsController
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODeadlock using AFIncrementalStore and NSFetchedResultsController
    primarykey
    data
    text
    <p>I've been bashing my head against this for a few days now and cannot for the life of me figure out what is going on. I'm pretty green with Core Data, but I know it well enough to avoid deadlock scenarios. However for this project I decided to try and incorporate AFIncrementalStore. I built a sample project to test the APIClient in order to map keys/values appropriately without messing with my actual project. It worked flawlessly.</p> <p>Now I'm using it in my actual project and things are finicky. The NSFetchedResultsController is used in a UITableViewController that gets pushed off screen (slide in menu similar to Facebook app). About 50% of the time I don't get a deadlock. I've made sure that the NSFetchedResultsController managedObjectContext is the same as my AppDelegate. Nearly everything is setup identical to the AFIncrementalStore examples. Even my sample project to test out the usage works perfectly. </p> <p>Here is an image of the Debug Navigator when I pause during the deadlock. It looks like the problem lies between AFIncrementalStore's background context and the main thread's context. However I'm not sure what to do since I didn't write AFIncrementalStore and am just going off of the existing docs/examples.</p> <p><img src="https://i.stack.imgur.com/XVA2L.png" alt="Debug Navigator"></p> <p>edit: Adding the backtrace of the 2nd thread</p> <pre><code>thread #2: tid = 0x2103, 0x925d180e libsystem_kernel.dylib`semaphore_wait_trap + 10 frame #0: 0x925d180e libsystem_kernel.dylib`semaphore_wait_trap + 10 frame #1: 0x0258cf08 libdispatch.dylib`_dispatch_thread_semaphore_wait + 16 frame #2: 0x0258ab3a libdispatch.dylib`_dispatch_barrier_sync_f_slow + 149 frame #3: 0x0258aa5c libdispatch.dylib`dispatch_barrier_sync_f + 37 frame #4: 0x00b64c8b CoreData`_perform + 187 frame #5: 0x00b67659 CoreData`-[NSManagedObjectContext(_NestedContextSupport) managedObjectContextDidUnregisterObjectsWithIDs:] + 73 frame #6: 0x00bdf2db CoreData`__97-[NSManagedObjectContext(_NestedContextSupport) managedObjectContextDidUnregisterObjectsWithIDs:]_block_invoke_0 + 75 frame #7: 0x00b64cc1 CoreData`internalBlockToNSManagedObjectContextPerform + 17 frame #8: 0x0259b014 libdispatch.dylib`_dispatch_client_callout + 14 frame #9: 0x0258ad5f libdispatch.dylib`_dispatch_barrier_sync_f_invoke + 58 frame #10: 0x0258aaa3 libdispatch.dylib`dispatch_barrier_sync_f + 108 frame #11: 0x00b64c8b CoreData`_perform + 187 frame #12: 0x00b67659 CoreData`-[NSManagedObjectContext(_NestedContextSupport) managedObjectContextDidUnregisterObjectsWithIDs:] + 73 frame #13: 0x00b71c8c CoreData`-[NSManagedObjectContext(_NSInternalAdditions) _disposeObjects:count:notifyParent:] + 444 frame #14: 0x00b71305 CoreData`-[NSManagedObjectContext(_NSInternalAdditions) _dispose:] + 597 frame #15: 0x00b70e15 CoreData`-[NSManagedObjectContext _dealloc__] + 325 frame #16: 0x00bd872f CoreData`internalBlockToDeallocNSManagedObjectContext + 79 frame #17: 0x0259b014 libdispatch.dylib`_dispatch_client_callout + 14 frame #18: 0x0258b418 libdispatch.dylib`_dispatch_queue_drain + 239 frame #19: 0x0258b2a6 libdispatch.dylib`_dispatch_queue_invoke + 59 frame #20: 0x0258c280 libdispatch.dylib`_dispatch_root_queue_drain + 231 frame #21: 0x0258c450 libdispatch.dylib`_dispatch_worker_thread2 + 39 frame #22: 0x971cde12 libsystem_c.dylib`_pthread_wqthread + 441 </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USrnystrom
    1. USrnystrom
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODeadlock using AFIncrementalStore and NSFetchedResultsController
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODeadlock using AFIncrementalStore and NSFetchedResultsController
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI haven't used AFIncrementalStore before, but do you need to manually merge the AFIncrementalStore context to the main AppDelegate context? It's a common core data deadlock when fetchedresultscontroller is working side by side with some sort of core data import.
      singulars
      1. PODeadlock using AFIncrementalStore and NSFetchedResultsController
      1. USTerence Yan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload