Geek Answers Handbook

Android Multithreading - WaitForGcToComplete after sending application to background

I use Android L for some multi-threaded operations, using several ThreadPoolExecutors to start AsyncTasks queues.

When my application goes to the background, I start to see numerous magazines for ...

I/art: WaitForGcToComplete blocked for ##.#####ms for cause XXXXX

... with random ...

I/art: No such thread id for suspend: ### .

It seems obvious that something is happening that makes the GC longer than expected. The log is generated by art / runtime / gc / heap.cc deep in AOSP. The second log message indicates that it is probably related to my thread pools. It is unclear why this only happens (for example, when you log in) when the application is sent to the background.

I did not see any failures because of this, but I have a lot more tests to pass. Has anyone encountered issues matching these magazines?

+7
garbage-collection android multithreading
source share

No one has answered this question yet.

See related questions:

3606
Close / hide Android soft keyboard
3295
Why is the Android emulator so slow? How can we speed up Android emulator development?
3288
Correct use cases for Android UserManager.isUserAGoat ()?
2609
Is there a unique identifier for an Android device?
2510
How to keep Android activity state by saving instance state?
2097
Is there a way to run Python on Android?
1858
"Debug certificate expired" error in Android Eclipse plugins
1844
What is "Context" on Android?
1074
How do servlets work? Create, Sessions, Shared Variables, and Multithreading
815
Android "Only the original thread that created the view hierarchy can touch its views."

More articles:


All Articles