Frame for Android systrace

I run systrace in my application to identify problems. One of my cases throws a warning in a systrace html report:

Work on the creation of this frame was planned for several milliseconds, which contributed to the fragmentation. Make sure that the code in the user interface thread does not block the work performed by other threads, and that background threads (such as network or bitmap downloads) are running on android.os.Process # THREAD_PRIORITY_BACKGROUND or lower, so they are less likely to interrupt the user interface thread. These background threads should be displayed with a priority number of 130 or higher in the planning section of the kernel process.

I understand the warning, but I see no reason why this is happening in my trace report. Below I have attached the frame in question, is there any information about what causes this problem?

Systrace Frame

+5
source share

All Articles