App won't launch again after user quits, only in 10.3, because of a thread?
App won't launch again after user quits, only in 10.3, because of a thread?
- Subject: App won't launch again after user quits, only in 10.3, because of a thread?
- From: "Crichlow, Eric" <email@hidden>
- Date: Wed, 28 Jan 2004 16:34:49 -0500
My application sometimes refuses to launch a second time, after the user
quits it the first time.
I get an error that says: "The operation could not be completed. An
unexpected error occurred (error code -600)."
After doing some testing, it appears as though the OS still thinks the
app is running. I found this out by trying to trash the application, but the
Finder won't let me because it says the app is open. Well, I check Activity
Monitor and see that the app isn't running anymore, but you can't convince
the Finder of that.
I have narrowed the situation down somewhat. This problem only happens
in 10.3 (10.3.2). Everything works fine in 10.2.x.
The problem only happens when there was a second (or more) thread
running at the time the app exited. The second thread exists to establish a
connection to a Bluetooth device.
Obviously there's no way to manually kill one NSThread from another. But
I would think the system would clean things up well enough that this problem
wouldn't exist. On some systems I've tried this on, the only way to get the
app to run again is to log out and log back in. On another system just
waiting a few moments is enough for it to work again.
What could keep a secondary thread from exiting when the application
that spawned it exits?
...Thanx...
...Eric...
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.