On Sep 26, 2012, at 10:08 , Kyle Sluder <[email protected]> wrote:
> Can you log +[NSBundle allBundles] and/or use Instruments to see what file
> access Foundation is performing and what responses it's getting back?
The difficulty is that this exception has never happened to me during
development. By chance (maybe), it happened for 2 customers yesterday -- though
it had been fine earlier in the day for one of them -- and when I sent them
debug versions with NSBundle logging code the problem disappeared. Of course
that made them happy ("fixed!"), but it didn't really get me anywhere.
I'm wondering, somewhat randomly, whether this is not something asynchronous,
but perhaps something subtler like a missing write barrier. For example, if a
separate process is involved in either loading the framework or loading the
nib, and there's a missing write barrier for a value being returned to the app
process, so that the processor caches were inconsistent, then it would only
fail if the separate process happened to run in a different core and would only
fail for a short while till the caches were consistent again. But this is
beyond my competence, so it's probably just a fantasy.
_______________________________________________
Cocoa-dev mailing list ([email protected])
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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
