LeakCanary优化：如何加快内存泄漏检测速度？

Absolutely! You can cut down that frustrating 1-2 minute wait for LeakCanary's leak alerts in Debug mode—this is super helpful when you're iterating on fixes and need quick feedback. Here's how to force GC and trigger immediate leak checks:

1. Manually Trigger GC + Force LeakCanary Checks #

You can explicitly ask the system to run GC and tell LeakCanary to skip its default waiting period right after you close an Activity. Add this code wherever makes sense for your testing workflow—like in the Activity's onDestroy() method, or even a debug-only floating button for manual triggers:

if (BuildConfig.DEBUG) {
    // Suggest to the system to run GC (effective in Debug mode with free memory)
    System.gc()
    // Force LeakCanary to run leak checks immediately, skipping default delays
    AppWatcher.INSTANCE.triggerGcAndRunChecks()
}

• System.gc() is a hint to the JVM to perform garbage collection. While it’s not a 100% guarantee, in Debug builds with plenty of free memory, it almost always cleans up unused objects like your closed Activity.
• triggerGcAndRunChecks() tells LeakCanary to skip its default 5-second wait and immediately verify if watched objects (like your Activity) were properly recycled.

2. Tweak LeakCanary's Global Configuration #

For a permanent Debug-mode fix, customize LeakCanary's settings to shorten delays and prioritize fast detection. Add this to your Application class:

class MyApp : Application() {
    override fun onCreate() {
        super.onCreate()
        if (BuildConfig.DEBUG) {
            LeakCanary.config = LeakCanary.config.copy(
                // Shorten wait time after an object is suspected to be leaked
                watchDelayMillis = 1000, // Default is 5000ms (5 seconds)
                // Enable immediate heap dumps when debugging
                dumpHeapWhenDebugging = true
            )
        }
    }
}

• watchDelayMillis reduces the time LeakCanary waits before confirming a potential leak.
• dumpHeapWhenDebugging skips extra waiting steps and directly triggers a heap dump as soon as a leak is suspected, cutting down total alert time.

3. Use LeakCanary's Built-In Debug Shortcuts #

LeakCanary adds a debug-only notification (or launcher icon, depending on your version) with options like "Dump Heap" or "Run Leak Checks". Tap it to manually trigger analysis without writing extra code—perfect for one-off tests.

A Quick Heads-Up #

Never force GC in Release builds—it disrupts the system's optimized garbage collection schedule and hurts performance. Always wrap these tweaks with BuildConfig.DEBUG guards to keep them limited to testing environments.

Even with these steps, heap dump analysis might take a few seconds (depending on your app's memory usage), but it’s way faster than waiting 1-2 minutes for the default workflow.

内容的提问来源于stack exchange，提问作者Damn Vegetables