-
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
Android 6.0 Heap dump parsing failure #267
Comments
Can you provide me with the stacktrace for |
@pyricau here you go:
|
Also seeing this one
|
@kylefowler got this one too. Could you confirm it happens on Marshmallow only? |
yeah, only seeing it on M |
@pyricau Any progress on this (six weeks since last activity)? LeakCanary seems unusable on Marshmallow (even with 1.4-SNAPSHOT). Is there any workaround? Saw your talk on Droidcon NYC and thought I'd give it a try ... Thanks! |
+1 |
+1 //For retrolambda
//Avoid applying new permission model for now, only one man ;) |
+1 just found out about this tool and was excited to use it, but since I'm on M I get this error every time :( |
|
Crash every day:1.3.1:
Detail:
|
+1 |
+1 |
+1 @pyricau Any progress on this ? |
+1 |
+1 Nexus 5 with Marshmallow too, thanks for the software ~ |
+1. Useless for Android 6+. Pls fix it. On Android<6 works perfect. Great job! |
+1 |
6 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 Nexus 6 ,Android 6.0 |
+1 |
2 similar comments
+1 |
+1 |
+1. Just tried to use this great tool but got stuck. |
+1 |
2 similar comments
+1 |
+1 |
+1 I'd love to use leakcanary, but this is killing me. |
this is still occurring while testing the snapshot and should not be closed Opened #358 as I don't have permission to reopened closed bugs |
I bumped to 1.4-SNAPSHOT and it didn't help. Started working after I uninstalled the application and did a clean build. |
it can't fix it |
Please make sure you use |
For me, it did not work on the 1.4-beta1, but it started working when i switched to 1.4-SNAPSHOT |
same issue |
This happens on both: 1.3.1 and 1.4-SNAPSHOT
The text was updated successfully, but these errors were encountered: