-
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
java.lang.StackOverflowError on HeapAnalyzerService #3
Comments
This is very interesting. It's happening in the service process, so that's when we're processing a heap dump. |
It was on my first run with leakcanary enabled... will try to reproduce later... |
Could you find the root of the stack in logcat? I'd like to know in which part of LeakCanary code this happened. |
My best bet here is that this happens when we try to start
I will close for now, please reopen or create a new one if you can get more info. |
Hi @pyricau , I also got this StackOverFlow on my first run with LeakCanary. My Logcat is similar but not equal to @luciofm
Let me know if I can help, as I've been able to isolate it to 1 specifc use case. Plus, after the crash I'm seeing this message in Logcat D/AndroidHeapDumper( 1256): Could not dump heap, previous analysis still is in progress. Maybe you can reopen the issue? |
Is this systematic? |
yes, it happens every time. |
Can you attach a debugger? Would be really handy if you could put a breakpoint in the StackOverflowError constructor to see what chain of objects it's attempting to serialize. |
@swankjesse The crash doesn't happen when I attach a debugger, but it occurs systematically without it. I'm going to try to add it as a local dependency and see if I can Log something. Any hint? |
It's only happening on Android 4.4.4, it seems to work well on Lollipop. And, one time it also worked well on KitKat. I haven't been able to capture any log, sorry. I've tested on Genymotion Nexus 4 and a real device One Plus One still on CM 11 |
@Maragues I bet crash doesn't happen with debugger attached because of this |
Happening to me too on Android 4.3 |
Finally got correct stacktrace:
|
Culprit: We could spend some time improve the serialized classes to avoid recursive calls. But after looking at it, I realized that the whole point is to save the parsing so that it can be reopened quickly later without reparsing the heapdump. We don't care about that. So we can probably get away with remove that part entirely. |
Fix in HAHA here: square/haha#4 |
Not just yet, need to update leakcanary. |
Updating to HAHA 1.3 which doesn't save its index file any more. Will hopefully resolve #3 (although there might be other issues down the road).
Updating to HAHA 1.3 which doesn't save its index file any more. Will hopefully resolve square#3 (although there might be other issues down the road).
After navigating a while through my app I got a StackOverFlowError...
The text was updated successfully, but these errors were encountered: