We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We're receiving crashlytics reports on Samsung devices following updating from version 2.8.1 to 2.9.1
Fatal Exception: java.io.IOException close failed: EACCES (Permission denied) libcore.io.IoBridge.closeAndSignalBlockedThreads (IoBridge.java:315) java.nio.channels.spi.AbstractInterruptibleChannel.close (AbstractInterruptibleChannel.java:116) shark.ThrowingCancelableFileSourceProvider$openRandomAccessSource$1.close (ThrowingCancelableFileSourceProvider.kt:43) shark.ConstantMemoryMetricsDualSourceProvider$openRandomAccessSource$1.close (ConstantMemoryMetricsDualSourceProvider.kt:63) shark.RandomAccessHprofReader.close (RandomAccessHprofReader.kt:51) shark.HprofHeapGraph.close (HprofHeapGraph.kt:230) kotlin.io.CloseableKt.closeFinally (Closeable.kt:57) leakcanary.internal.AndroidDebugHeapAnalyzer.analyzeHeap (AndroidDebugHeapAnalyzer.kt:155) leakcanary.internal.AndroidDebugHeapAnalyzer.runAnalysisBlocking (AndroidDebugHeapAnalyzer.kt:59) leakcanary.internal.AndroidDebugHeapAnalyzer.runAnalysisBlocking$default (AndroidDebugHeapAnalyzer.kt:46) leakcanary.BackgroundThreadHeapAnalyzer$onEvent$1.run (BackgroundThreadHeapAnalyzer.kt:24)
The text was updated successfully, but these errors were encountered:
Interesting, looks like we're failing to close? I wonder what could possibly have changed in 2.9
Sorry, something went wrong.
Ignore failure to close file
5528f4d
Fixes #2382
Successfully merging a pull request may close this issue.
Description
We're receiving crashlytics reports on Samsung devices following updating from version 2.8.1 to 2.9.1
Version Information
Additional Information
The text was updated successfully, but these errors were encountered: