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
AFAIK there's no silver bullet, sorry. Just your skill at debugging:
narowwing down the problem, correlating the problem, studying log
files, studying stack traces, stepping through the code...
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group
adb logcat?
On Aug 11, 5:21 pm, sdphil 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 s
bump.
On Aug 11, 2:21 pm, sdphil 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 somethi
4 matches
Mail list logo
