Hi, I have developed an application (including a native library) that sometimes freezes the phone (becomes completely non-responsive) and after a while I get:
W/WindowManager( 184): Key dispatching timed out sending to... The 'top' command shows that my application is stealing 97% of CPU which is not quite expected behaviour. I suspect that the application hangs in an endless loop somewhere, but I have no idea where. Not even if it is in the native library written i C++, or in the Java part. What kind of debugging mechanisms are available in this case? I've had a quick look at 'traceview' but the problem is that I have to call Debug.stopMethodTracing() to write profiling data from the recording buffer to file, and I am of course unable to make that call after the endless loop. Any ideas anyone? /Martin -- 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
