Databases
StackOverflow2013
Postsdbo
POEXC_BAD_ACCESS when trying to access a managed object property
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POEXC_BAD_ACCESS when trying to access a managed object property
    primarykey
    data
    text
    <p>I'm having some trouble dealing with Core Data+concurrency/nested MOCs (not sure which one I'm having problems with =P).</p> <p>I have a method where I pass in a managed object ID (I checked that it's permanent) and that method has a child managed object context that is confined to a certain queue. I can retrieve the object from the child managed object context via <code>[managedObjectContext objectWithID:moID]</code> but when I try to access any of its properties (the managed object is still a fault), I get <code>EXC_BAD_ACCESS</code> with the stack trace showing <code>_svfk_1</code> and <code>objc_msgSend</code>.</p> <p>I know it's kind of difficult to figure out what the problem is without sample code, but I was hoping someone could shed some light on the possible causes. Thanks. =)</p> <p><strong>EDIT:</strong> I tried using <code>existingObjectWithID:error:</code> instead of <code>objectWithID:</code> as Tom Harrington suggested and now it works sometimes but doesn't work other times. I also experienced an <code>EXC_BAD_ACCESS</code> crash on <code>mergeChangesFromContextDidSaveNotification:</code>. I suspect this could be a synchronization issue. If I edit something in one context and save while something else is edited in my child context, would that cause an issue?</p> <p><strong>EDIT 2:</strong> I figured out why existingObjectWithID:error: was working sometimes but not always. The managed object ID was indeed a temporary ID (shouldn't <code>mergeChangesFromContextDidSaveNotification:</code> convert it to a permanent ID?), so I had to call <code>obtainPermanentIDsForObjects:error:</code> before passing the ID. But I'm still getting crashes sometimes in the child context's <code>mergeChangesFromContextDidSaveNotification:</code>. What could be the possible causes of this? Thanks.</p> <p><strong>EDIT 3:</strong> Here's what my MOC hierarchy looks like.</p> <pre><code> Persistent Store Coordinator | Persistent Store MOC / \ Main Queue MOC Child MOC (confinement) </code></pre> <p>I'm invoking a method from the main queue that uses the Child MOC (in another queue) to insert and update some managed objects and at the same time, I'm inserting and updating managed objects in the Persistent Store MOC. Managed objects can also be updated, deleted, and inserted in the Main Queue MOC at the same time. I merge any changes from the Persistent Store Coordinator to both the Main Queue MOC and the Child MOC.</p> <p>Some more questions: Does saving an MOC automatically merge things? If there is a pending merge request for an MOC and you save before that merge request is processed, can that cause issues?</p> <p><strong>EDIT 4:</strong> Here's how I initialize the Child MOC.</p> <pre><code>dispatch_sync(_searchQueue, ^{ _searchManagedObjectContext = [[NSManagedObjectContext alloc] initWithConcurrencyType:NSConfinementConcurrencyType]; [_searchManagedObjectContext setParentContext:_persistentStoreManagedObjectContext]; [_searchManagedObjectContext setMergePolicy:NSMergeByPropertyStoreTrumpMergePolicy]; }); </code></pre> <p>Btw, I notice that the merge only crashes (with <code>EXC_BAD_ACCESS</code>) when the notification contains deleted objects.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USfumoboy007
    1. USfumoboy007
    plurals
    1. 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. POEXC_BAD_ACCESS when trying to access a managed object property
      1. USfumoboy007
      1. VTBountyStart
    2. VO
      singulars
      1. POEXC_BAD_ACCESS when trying to access a managed object property
      1. USenjayem
      1. VTFavorite
    3. VO
      singulars
      1. POEXC_BAD_ACCESS when trying to access a managed object property
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COOh: "The data in the persistent store represented by objectID is assumed to exist—if it does not, the returned object throws an exception when you access any property (that is, when the fault is fired)." Let me check up on this.
      singulars
      1. POEXC_BAD_ACCESS when trying to access a managed object property
      1. USfumoboy007
    2. CONope, I added a breakpoint in `prepareForDeletion` in my managed object subclass, but it was never fired. So the managed object has not been deleted when I call this method.
      singulars
      1. POEXC_BAD_ACCESS when trying to access a managed object property
      1. USfumoboy007
    3. COdo you use performBlock to talk to the child MOC (I assume that's not on main queue)?
      singulars
      1. POEXC_BAD_ACCESS when trying to access a managed object property
      1. USDmitry Shevchenko
 

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