07-16-2009 04:05 AM
Solved! Go to Solution.
07-16-2009 07:22 AM - edited 07-16-2009 07:25 AM
07-19-2009 08:52 AM - edited 07-19-2009 08:56 AM
OK. Finally fixed this!
It appears that the PushRegistry mechanism was still alive in the background, not allowing the application to close gracefully. More specifically: RIM's helper thread MIDletMain.MIDletPushRegistryWorkerThread was deadlocked. I have no idea why and frankly I don't have time to investigate it. For now I just shut down PushRegistry and the app quits fine.
I think deserve a Kudos for this, if only for my Ego's sake... nudge... nudge...
Aa I understand, there are quite a few people who ran into similar problems, where MIDlets won't quit on BlackBerry. So I thought I'd elaborate on how I located the solution:
I ran the app in the Eclipse debugger, then quit it and looked at the lis of active threads. Normally, after quitting the app., all associated threads should die. So, one of the remaining threads associated with the app. is the culprit:
09-02-2009 03:31 PM