Android应用内存分析异常：Profiler使用时应用冻结求助

Hey there, sorry to hear you're stuck dealing with both the Profiler freezing up and persistent OutOfMemoryErrors in your app. Let's break this down step by step—first we'll fix the Profiler issue so we can properly diagnose the root cause of your OOM problems.

First, let's decode your Logcat clues #

The repeating error E/zygote: E[0]:Timed out waiting for threads to suspend is the core reason the Profiler is freezing. This means Android Studio's Profiler can't pause your app's threads to collect memory data, leading to timeouts that eventually hang your app.

Here are actionable fixes to get the Profiler working again:

• Check for unresponsive Native threads: If your app uses NDK/native code, some threads might be blocking or ignoring the signals the Profiler relies on to suspend threads. Use adb shell ps -T <your-app-pid> to list all active threads, then verify that native threads aren't stuck in infinite loops without handling signals like SIGQUIT. You may need to adjust your native code to allow proper thread suspension.

• Disable Instant Run: Instant Run often interferes with the Profiler's ability to attach to your app. Head to Settings > Build, Execution, Deployment > Instant Run and uncheck "Enable Instant Run...", then restart Android Studio and rebuild your app from scratch.

• Switch to Sampled Memory Tracking: The default live memory tracking mode is resource-heavy. In the Memory Profiler panel, click the settings icon (⚙️) in the top-left corner, then select Sampled instead of Live. This reduces overhead and avoids triggering thread suspension timeouts.

• Update Android Studio & SDK Tools: Older versions of the Profiler had known bugs with thread suspension. Update to the latest stable version of Android Studio, along with SDK Platform Tools—many of these compatibility issues get patched in newer releases.

• Alternative OOM debugging tools (while fixing Profiler): If the Profiler won't cooperate right away, use these workarounds to start diagnosing OOM:

  • Run adb shell dumpsys meminfo br.com.xxxxx to get a quick snapshot of your app's memory usage, including heap sizes and allocated objects.
  • Integrate LeakCanary into your app—it automatically detects memory leaks and gives detailed reports without needing the Profiler.

Once Profiler is working, focus on the OutOfMemoryError: #

When you can successfully use the Memory Profiler, keep an eye out for these red flags:

• A steady upward trend in heap memory usage (a clear sign of memory leaks)
• Large objects (like Bitmaps) that aren't being recycled properly
• Frequent short-lived object creation (memory jitter) that triggers constant GC cycles

Your Logcat Output: #

2019-04-09 08:42:41.151 19728-20399/br.com.xxxxx V/StudioProfiler: Live memory tracking enabled.
2019-04-09 08:42:41.151 19728-20399/br.com.xxxxx V/StudioProfiler: JNIEnv not attached
2019-04-09 08:42:41.483 19728-20399/br.com.xxxxx V/StudioProfiler: Loaded classes: 8894
2019-04-09 08:42:51.688 19728-20399/br.com.xxxxx E/zygote: E[0]:Timed out waiting for threads to suspend(br.com.xxxxx), waited for 10.000s
2019-04-09 08:43:01.689 19728-20399/br.com.xxxxx E/zygote: E[0]:Timed out waiting for threads to suspend(br.com.xxxxx), waited for 20.000s
2019-04-09 08:43:11.689 19728-20399/br.com.xxxxx E/zygote: E[0]:Timed out waiting for threads to suspend(br.com.xxxxx), waited for 30.000s

Android Studio Profiler Freeze Screenshot: #

内容的提问来源于stack exchange，提问作者Pedro Malta