square/leakcanary

Running heap analysis in separate process does not invoke custom OnLeakFoundCallback callback

Open

#1,789 建立於 2020年3月30日

在 GitHub 查看
 (5 留言) (0 反應) (0 負責人)Kotlin (29,920 star) (3,975 fork)batch import
good first issuestatus: help wantedtype: documentationtype: enhancement

描述

Description

Not sure if this is the expected behavior or not. I was expected to have background process trigger callback on the main process with leak analysis data.

Steps to Reproduce

  1. Follow https://square.github.io/leakcanary/recipes/#running-the-leakcanary-analysis-in-a-separate-process
  2. Use a app that has custom OnLeakFoundCallback callback
  3. Make sure dumpHeapWhenDebugging is set to true if using debugger
  4. Verify once that callback is not invoked once analysis complete (via debugger breakpoint or logcat)

Expected behavior:

Callback to be invoked in main process.

Version Information

  • LeakCanary version: 2.2
  • Android OS version: API 29
  • Gradle version: n/a

貢獻者指南

技術棧
kotlinandroid
領域
mobile
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Android developmentKotlinLeakCanary basics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
55
研究方向
Investigate LeakCanary's source code for the separate process heap analysis implementation, focusing on classes related to OnLeakFoundCallback and inter process communication. Check the main process handling of analysis results, likely in the HeapAnalyzerService or related components. Review comments and linked issues for context on the expected behavior.