Skip to content
New issue

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

StrickMode violation: Leaded Closable #9

Open
ninovanhooff opened this issue Jun 22, 2022 · 0 comments
Open

StrickMode violation: Leaded Closable #9

ninovanhooff opened this issue Jun 22, 2022 · 0 comments

Comments

@ninovanhooff
Copy link
Collaborator

ninovanhooff commented Jun 22, 2022

This vciolation is always triggered when running the sample app

2022-06-22 14:20:20.544 21722-21734/com.q42.q42stats.sample.debug 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:1992)
        at dalvik.system.CloseGuard.warnIfOpen(CloseGuard.java:347)
        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:920)

This may or may not be a false alarm. At the moment of writing, this SO Post has no resolution:

https://stackoverflow.com/questions/65011420/strictmode-policy-violation-android-os-strictmode-leakedclosableviolation-in-my

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant