I think I have fixed it now. I discovered that lots of objects were created over and over again for every screen turn in the view constructor. I fixed this by making the these objects static. I mailed the new version to you. You got it for free, it will cost 4,5 $ in the appstores:)
On 3 Dec, 10:23, Eyvind Almqvist <[email protected]> wrote: > I got this test result from SonyEricsson: > > We have tested your latest version which you send to me. The rotation > issue still can reproduce on both android 1.6 and 2.1. And the > reproducibility of this issue is much higher than before. On 1.6, theappwill > force closed after I rotate the screen more than 2 times. > > This is very strange. I thougth that I fixed the rotation problem and > they say that it is worse now... > > On 2 Dec, 20:38, Eyvind Almqvist <[email protected]> wrote: > > > > > Thanks, I read the article. Then I saw that I had a global reference > > to a context, which I didn't need. I removed it and then it worked > > much smoother. I think this fixed the leak. I don't have any reference > > to a context at all now. I mailed youmyapp. Hope it works like it > > should on your HTC! > > > On 2 Dec, 14:48, Yahel <[email protected]> wrote: > > > > > > When they rotate the screen several times, > > > > This is usually a symptom of a memory leak. > > > > Try to read this article from Romain Guy > > > :http://www.curious-creature.org/2008/12/18/avoid-memory-leaks-on-andr... > > > > It explains how they can happen from a single handle to the context. > > > > The fact that you do not have crash but again this black screen(no > > > drawing being done) probably means that you actually handle this > > > exception with a try catch somewhere. Ifmyguess is correct then you > > > simply have to put a Log.e("error","error happens here : xxx"); in > > > every catch of yourappand you'll find where it happens. Again the > > > difficulty is to be able to reproduce the problem. > > > > Again you should implement something like the android-remote- > > > stacktrace so that when it happens on someone devices you get the > > > stacktrace from their session which will give you good clues on what's > > > happening. > > > > “Sorry! Activity XXX(in application XXX) is not responding” happens > > > when you have a very long operation that hangs the main UI thread so > > > that the user can't use it anymore. Maybe this is a clue for you to > > > what is happening. Do you have a long calcultation, double buffering > > > drawing, loading of a big bitmap or something similar in the main > > > thread ? > > > > If you tell me which game it is I can try to reproduce the problem > > > onmyHTC Hero which is an older phone so might be more sensitive to the > > > problem. > > > > Yahel- Dölj citerad text - > > > - Visa citerad text -- Dölj citerad text - > > - Visa citerad text - -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
