Well, does it ask if you want to Force Close? If not, it sounds like there isn't clearly a problem. You'll probably never understand every line in logcat.
On Wednesday, August 15, 2012 8:49:24 AM UTC-5, b0b wrote: > > I have an app whose initialization is quite CPU and thread heavy for 3-5s > on startup. > > During that period, the logcat reports several: > > 08-15 15:33:24.804: I/dalvikvm(8550): threadid=3: reacting to signal 3 > 08-15 15:33:24.882: I/dalvikvm(8550): Wrote stack traces to > '/data/anr/traces.txt' > > every 500ms or so it seems. > > AFAIK the main (UI) thread is not blocked as all heavy initialization work > is done in threads as it should. > However there are a lot of concurrent stuff with many threads hapenning > during these 3-5s with the CPU probably at 100%. > > I suspect that writing '/data/anr/traces.txt' several times on startup > further slow it down. > > I'm asking for details on how the system detect ANRs and in particular > under which conditions it produces logcat output above. > Is it linked to CPU usage or simply the main thread being blocked ? > That is, one or several threads pegging the CPU would give these messages > (while the main thread itself is not blocked) ? > > > > -- 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
