Consider pausing debugger when you think ANR is about to occur. Basically, ANR pops up when your UI thread (main thread) can't dispatch UI event message queue for more than 5 sec. (it could be less - that's just my guess). So basically, you're loading your UI thread with some heavy worka and he has no chance to dispatch messages from Looper's queue.
On Aug 12, 12:21 am, sdphil <phil.pellouch...@gmail.com> wrote: > hi. what is the best way to debug ANR. ideally, it would be nice to > know what call / thread / file and line number it is stalled at when > the ANR occurs, but every time I look at /anr/traces.txt, I can't seem > to find anything that points to something I can start tracking down. > > tia. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
