square/leakcanary

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

Open

#1 789 ouverte le 30 mars 2020

Voir sur GitHub
 (5 commentaires) (0 réactions) (0 assignés)Kotlin (3 975 forks)batch import
good first issuestatus: help wantedtype: documentationtype: enhancement

Métriques du dépôt

Stars
 (29 920 stars)
Métriques de merge PR
 (Aucune PR mergée en 30 j)

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

Guide contributeur