square/leakcanary

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

Open

#1,789 opened on Mar 30, 2020

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Kotlin (29,920 stars) (3,975 forks)batch import
good first issuestatus: help wantedtype: documentationtype: enhancement

Description

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

Contributor guide

Tech stack
kotlinandroid
Domain
mobile
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Android developmentKotlinLeakCanary basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
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.