re: EXC_BAD_ACCESS when migrating a store, but only sometimes...
re: EXC_BAD_ACCESS when migrating a store, but only sometimes...
- Subject: re: EXC_BAD_ACCESS when migrating a store, but only sometimes...
- From: Ben Trumbull <email@hidden>
- Date: Thu, 29 Oct 2009 11:17:02 -0700
> I've come across a rather perplexing problem which is driving me nuts.
> I'm attempting to migrate a core data SQLite store to the current
> model version, and most of the time it works fine. However, sometimes
> I get an EXC_BAD_ACCESS in the following stack:
>
> objc_assign_strongCast + 19
> -[NSMigrationManager
> migrateStoreFromURL:type:options:withMappingModel:toDestinationURL:destinationType:destinationOptions:error
> :] + 2750
> (My methods...)
If you can reproduce it in a small sample project (with your models, etc, but the least amount of custom code), then please file a bug.
One thing you might try is, before creating the NSMigrationManager with -[NSMigrationManager initWithSourceModel:destinationModel:] is creating 2 empty throw away PSCs, one that uses the source model and one that uses the destination model. Then just release the PSCs and use those models to construct the NSMigrationManager. That should work around the one known GC issue here.
If you're not using GC, than try breaking out Instruments' ObjectAlloc with NSZombie detection.
- Ben
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden