Uses a processor in the background without doing anything

When the Android application (JNI + Java) switches to the background mode, then based on the Elixir monitor, a 40-80% processor is required for no apparent reason. Logcat has no indication of any real activity; the DDMS method profiler does not find method calls.

In fact, after a few minutes, the OS (ISC), at least sometimes, seems to fix it automatically: it restarts the application process, and then it as expected - taking 0% of the CPU and some memory. When I run the application again and click on the house to take it into the background, the same processor hangs.

Any ideas you can explore?

+4
source share
1 answer

So, my conclusion: 1. If the method calls are not shown in Profiler, then most likely this means that the CPU is wasted on the NDK side. 2. GDB-based profiling should be used there, perhaps something like that

+2
source

All Articles