Re: NSProgressIndicator, runModalForWindow, detachNewThreadSelector -> Not good...
Re: NSProgressIndicator, runModalForWindow, detachNewThreadSelector -> Not good...
- Subject: Re: NSProgressIndicator, runModalForWindow, detachNewThreadSelector -> Not good...
- From: Dix Lorenz <email@hidden>
- Date: Tue, 4 Apr 2006 19:04:09 +0200
On 04.04.2006, at 17:23, Cameron Hayne wrote:
On 4-Apr-06, at 4:42 AM, Dix Lorenz wrote:
the program crashes:
#0 0x909c0120 in objc_msgSend
If you enable zombies as described in this Apple doc:
http://developer.apple.com/technotes/tn2004/tn2124.html
you should be able to see what object is causing the crash and that
should be enough of a clue to figure out what is happening.
Thanks for the advice, I am a bit closer but still clueless ;-) I get
2006-04-04 18:55:22.273 mediMACH IV[522] *** NSThread: ignoring
exception '*** -[_NSZombie forward::] not overridden!' that raised
during delayed perform of target 0x1b56f630 and selector
'_enableScreenUpdatesIfNeeded'
2006-04-04 18:55:22.273 mediMACH IV[522] *** Selector 'release' sent
to dealloced instance 0x1b56f630 of class NSWindow.
Break at '-[_NSZombie release]' to debug.
2006-04-04 18:55:22.273 mediMACH IV[522] *** Selector 'release' sent
to dealloced instance 0x1b56f630 of class NSWindow.
and the last line repeats very fast. So I assume I am overreleasing
the window but I don't know where. I let NSWindowController handle
everything, I don't retain or release the window anywhere. I only
pass it to runModalForWindow but that should be ok... If I break at -
[_NSZombie release] as suggested it breaks exactly where it will
sooner or later crash so that doesn't help.
Where can I go from here?
Thanks,
Dix
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden