The problem is, this happens randomly, on several unrelated Activities and there are no problems 99% of the time.
By the way I meant onCreate (not onStart) in my previous mail. In some of our Activities, we do lots of things in onCreate that might take too long (for instance in a few of them, we start a query in the main thread). We know it's a bad thing to do and we're in the process of fixing this. We do not see lots of ANRs though. But I was wondering if taking "too long" in onCreate could somehow lead to this behavior? Thanks again any hint is appreciated, BoD On Apr 13, 3:56 am, gjs <[email protected]> wrote: > Hi, > > Maybe post some of your code for onCreate, onStart, onResume so people > can review. > > Regards > > On Apr 13, 1:22 am, BoD <[email protected]> wrote: > > > Ps: I realize my problem is a bit vague, and that I unfortunately have > > few details to share to help understanding what's going on. > > > Maybe somebody can give me hints on what would be the best course of > > action to follow the next time I encounter this problem (like look at > > some specific logs, or put a breakpoint in some specific Android > > class...) ? > > > Thanks a lot for your help. > > > BoD > > > On Apr 11, 5:53 pm, BoD <[email protected]> wrote: > > > > Hello, > > > > We have a problem in our app that happens very rarely - but I have > > > witnessed it several times, on several devices and once on the > > > Emulator. > > > We currently do not know a way to reproduce it. > > > It goes like this: you use the app normally, you click on an item or a > > > button that starts an Activity (it seems it can happen anywhere in the > > > app, and not in one specific Activity). > > > => The Activity, instead of being started normally, seems to be > > > started "in a loop", thus producing a nice blinking/stroboscopic > > > effect. > > > > Exciting the app by pressing back several times, solves the problem: > > > if we then relaunch it, the problem won't be there and then we usually > > > won't see the problem for a few weeks/months. Hence the "Blinking > > > Activity of Death" nickname... > > > > Reading the logs, it looks like onStart() and onResume() are normally > > > called, again and again. > > > The only warning I see in the logs is this: > > > > INFO/UsageStats(102): Unexpected resume of <myapp> while already > > > resumed in <myapp> > > > > Googling a bit about this > > > (andhttp://stackoverflow.com/questions/3851363/what-is-going-on-with-the-...) > > > didn't help. > > > > The "Starting activity" and "Displayed activity" bits are logged only > > > once. > > > > I checked to be sure our startActivity or startActivityForResult calls > > > are not in any sort of loops. > > > > Any idea on what could produce such behavior? > > > Thanks a lot for your help. > > > > -- > > > BoD -- 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
