calls to principalClass causing freeze -- I'm stumped
calls to principalClass causing freeze -- I'm stumped
- Subject: calls to principalClass causing freeze -- I'm stumped
- From: Christopher Ashworth <email@hidden>
- Date: Wed, 11 Jul 2007 19:36:55 -0400
Hullo list,
What might cause a call to an NSBundle's principalClass method to
freeze, and how can I debug it?
I am receiving a number of reports from users that my plugin-based
application [1] is freezing on launch when some FireWire devices are
attached.
When extra logging is turned on for these users, their log shows the
freeze is occurring when loading one of the plugins during a call to
principalClass:
Class pluginClass = [(NSBundle *)plugin principalClass];
The app does not crash, but never gets past this call.
I purchased two of the FireWire devices causing this problem (an
Edirol FA-66 audio device and a Canopus ADVC 110 video I/O device)
but I cannot get this freeze to happen on any of my development
machines (PowerBook G4, MacBook Pro, Intel Mac Mini).
In desperation I went to the local Apple store and wandered around
plugging the devices into the display models, and was able to finally
see the freeze with my own eyes. I mailed copies of the system
profiles back to myself, but the quantity of information in those
profiles has made it difficult for me to find what the difference
might be between freezers and non-freezers.
I also found that the same devices can be successfully re-connected
after launch, and used without incident. The freeze only manifests
if they are connected during launch.
I'm not sure what to do at this point. Any tips would be greatly
appreciated!
Christopher
[1] http://figure53.com/qlab/
_______________________________________________
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