[TIMOB-1605] Android: KrollContext handler threads never quit
|Fix Version/s||Release 1.5.0 M01|
Backing out of windows that have contexts, or even backing out of the whole app, does not end the HandlerThread that the KrollContext runs in. If you back out of an app, for example, then reactivate it again from the home screen, you'll get a whole new set of threads, while the other ones will also still be hanging around (assuming Android never terminated the app to recover resources.) The same holds true if you open and close windows with contexts.
The behavior can be seen in this video:
(I accidentally go to the KitchenSink app a few times in that video -- ignore that.)
- Jeff Haynie 2011-04-15
(from [d2424ff557b69a39a573ebd1c2c53565a1b106dc]) Move the location of the Kroll release stuff from last commit. [#1605] http://github.com/appcelerator/titanium_mobile/commit/d2424ff557b69a39a573ebd1c2c53565a1b106dc"> http://github.com/appcelerator/titanium_mobile/commit/d2424ff557b69...
- Bill Dawson 2011-04-15
This has been fixed since August, not sure why I kept it open. I confirmed today that it's still fixed in 1.5.
- Thomas Huelbert 2011-04-15
closing - Titanium SDK version: 1.5.0 (12/08/10 14:51 55a4c32)