Crash when exploring an HeapDump

[Tolriq]

Description

Got a crash with 2.9.1 but can't reproduce again for now. Reporting in case there's something to look into.

Steps to Reproduce

Not 100% sure was while navigating inside an HeapDump or while leaving the heap dump screen. Can't reproduce despite many attempts.

Version Information

• LeakCanary version: 2.9.1
• Android OS version: 12
• Gradle version: 7.4.2

Additional Information

Log:

java.lang.IllegalStateException: Already closed
	at leakcanary.internal.activity.db.ScopedLeaksDb$DbOpener.checkClosed(ScopedLeaksDb.kt:69)
	at leakcanary.internal.activity.db.ScopedLeaksDb$DbOpener.getWritableDatabase(ScopedLeaksDb.kt:51)
	at leakcanary.internal.activity.db.Db$execute$1.invoke(Db.kt:35)
	at leakcanary.internal.activity.db.Db$execute$1.invoke(Db.kt:9)
	at leakcanary.internal.activity.db.Io$execute$2.invoke(Io.kt:44)
	at leakcanary.internal.activity.db.Io$execute$2.run(Io.kt:10)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
	at java.lang.Thread.run(Thread.java:920)

[pyricau]

Thanks! You just found a major crash, the UI only allows opening the db once.

Repro:

• Go to leaks
• Press back so that activity gets destroyed
• Go to leaks again => crash.

[Tolriq]

Nice is it worth a chocolate Cookie ? :)

I also just got some OOM during heap analysis, do you want an issue!? (Probably due to my app currently consuming wayy too much memory)

[dmytroKarataiev]

We're having the same crash, let me know if you need more info.