You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically, when I install a sample app, the app'll crash because of LeakedClosableObjects + detectDiskReads in Strictmode
it's quite similar as #782
According to this issue, I think that i have ideas to fix this. I suppose there are two things to do
If you agree on this, I can make a PR to fix this issue.
💣 Steps to reproduce
Go to app
See error
🔧 Expected behavior
the app shouldn't crash
📷 Screenshots
file.mp4
Addition context
D/StrictMode: StrictMode policy violation: android.os.strictmode.LeakedClosableViolation: A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks. Callsite: close
at android.os.StrictMode$AndroidCloseGuardReporter.report(StrictMode.java:1929)
at dalvik.system.CloseGuard.warnIfOpen(CloseGuard.java:305)
at sun.nio.fs.UnixSecureDirectoryStream.finalize(UnixSecureDirectoryStream.java:580)
at java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:291)
at java.lang.Daemons$FinalizerDaemon.runInternal(Daemons.java:278)
at java.lang.Daemons$Daemon.run(Daemons.java:139)
at java.lang.Thread.run(Thread.java:923)
📱 Tech info
Device: Pixe 2
OS: Android 11
Chucker version: 4.0.0-SNAPSHOT
The text was updated successfully, but these errors were encountered:
Basically, when I install a sample app, the app'll crash because of LeakedClosableObjects + detectDiskReads in Strictmode
Are you talking about the head of develop or another revision?
I've just tested it + I've also tried to enable StrictMode before super.onCreate but I wasn't able to reproduce.
Unless we have a consistent way to reproduce this, we can't really fix it.
Basically, when I install a sample app, the app'll crash because of LeakedClosableObjects + detectDiskReads in Strictmode
Are you talking about the head of develop or another revision? I've just tested it + I've also tried to enable StrictMode before super.onCreate but I wasn't able to reproduce.
Unless we have a consistent way to reproduce this, we can't really fix it.
Hello, it's the develop branch I've tested. It's wierd that on my side I can reproduce it like 100%.
✍️ Describe the bug
Basically, when I install a sample app, the app'll crash because of LeakedClosableObjects + detectDiskReads in Strictmode
it's quite similar as #782
According to this issue, I think that i have ideas to fix this. I suppose there are two things to do
StrictMode
beforesuper.onCreate
called according to the official site https://developer.android.com/reference/android/os/StrictModeLeakCanary
the related issue is here DiskReadViolation when calling LeakCanary.setConfig() in Application.onCreate() square/leakcanary#2117, so the fix needs to bump a version for this.If you agree on this, I can make a PR to fix this issue.
💣 Steps to reproduce
🔧 Expected behavior
the app shouldn't crash
📷 Screenshots
file.mp4
Addition context
📱 Tech info
The text was updated successfully, but these errors were encountered: