-
Notifications
You must be signed in to change notification settings - Fork 4k
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
StrictMode disk access violation #15
Comments
That's really interesting. I thought of We can work around that, delay the call to |
There's more to it than just that, we'll need to update http://github.com/square/haha as well. |
* Heap dumps and analysis results were previously saved in the app directory. They are now saved on the external storage (sd card). * Centralized internal static helper methods to a dedicated class: `LeakCanaryInternals`. BREAKING CHANGES * When upgrading, previously saved heap dumps will be lost, but won't be removed from the app directory. You should probably uninstall your app. * Added permission WRITE_EXTERNAL_STORAGE * Public API change: Removed `Application` parameter in `LeakCanary.androidWatcher()` * Public API change: Removed `Application` parameter in `AndroidHeapDumper()` * Fixes #21 (can't share heap dump) * This is a step towards fixing #15 (strict mode violations), although there's still more work.
As we found in #61, LeakCanaryInternals#setEnabled should be in background. |
* Enable Strict Mode thread policy in the sample app. * Fixed violation when cleaning up files on startup. * Fixed violation when enabling components, the other side of the binder does IO operations. Fixes #15
Fix Strict mode violations. Fixes #15.
Well done! |
* Heap dumps and analysis results were previously saved in the app directory. They are now saved on the external storage (sd card). * Centralized internal static helper methods to a dedicated class: `LeakCanaryInternals`. BREAKING CHANGES * When upgrading, previously saved heap dumps will be lost, but won't be removed from the app directory. You should probably uninstall your app. * Added permission WRITE_EXTERNAL_STORAGE * Public API change: Removed `Application` parameter in `LeakCanary.androidWatcher()` * Public API change: Removed `Application` parameter in `AndroidHeapDumper()` * Fixes square#21 (can't share heap dump) * This is a step towards fixing square#15 (strict mode violations), although there's still more work.
* Enable Strict Mode thread policy in the sample app. * Fixed violation when cleaning up files on startup. * Fixed violation when enabling components, the other side of the binder does IO operations. Fixes square#15
Fix Strict mode violations. Fixes square#15.
With
StrictMode
fully enabled:I'm getting a crash on launch when calling
LeakCanary.install(this);
Calling
LeakCanary.install()
on a background thread fixes the issue, just thought it may be worth addressing in the lib (or in the readme) since others may also haveStrictMode
fully enabled for debug builds.The text was updated successfully, but these errors were encountered: