Open GoogleCodeExporter opened 8 years ago
This is a pretty big problem. An extra thread is generated that never goes away
with every AdWhirlLayout created.
Orientation changes create one extra; the sleep cycle can cause two (or zero)
depending on the screen orientation. The only way the threads will terminate is
by manually shutting down the process with a task manager of some sort. Sooner
or later the system starts running out of resources and bad things start to
happen (*much* sooner if one happens to be debugging how an app handles
orientation changes!).
I posted two screen shots. One is of the stock 3.0 SDK from the download site
after 18 orientation/sleep events. It shows a new thread pool having been
created for every change, each with a new pid. The other is of our build after
30 such events showing a single process. The fix as described on the user forum
seems to do the trick (see my followup there -
http://groups.google.com/group/adwhirl-users/browse_thread/thread/ec7c58531b24a2
d2#).
Where are you guys at with this? Do you need/want to seem my code on that?
Original comment by goo...@yourarcade.com
on 19 Apr 2011 at 3:09
Attachments:
Original issue reported on code.google.com by
ob.l...@gmail.com
on 24 Mar 2011 at 1:10