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

LeakCanary v1.5 OOM bug #654

Closed
yitelu opened this issue Nov 10, 2016 · 8 comments
Closed

LeakCanary v1.5 OOM bug #654

yitelu opened this issue Nov 10, 2016 · 8 comments

Comments

@yitelu
Copy link

yitelu commented Nov 10, 2016

In com.roidapp.photogrid:5.32:306.

  • FAILURE in 1.5 00f37f5:java.lang.OutOfMemoryError: Failed to allocate a 11229144 byte allocation with 8388608 free bytes and 8MB until OOM
    at com.squareup.haha.trove.TLongHashSet.rehash(TLongHashSet.java:162)
    at com.squareup.haha.trove.THash.postInsertHook(THash.java:283)
    at com.squareup.haha.trove.TLongHashSet.add(TLongHashSet.java:146)
    at com.squareup.haha.perflib.analysis.TopologicalSort$TopologicalSortVisitor.doVisit(TopologicalSort.java:87)
    at com.squareup.haha.perflib.analysis.TopologicalSort.compute(TopologicalSort.java:36)
    at com.squareup.haha.perflib.Snapshot.computeDominators(Snapshot.java:311)
    at com.squareup.leakcanary.HeapAnalyzer.findLeakTrace(HeapAnalyzer.java:187)
    at com.squareup.leakcanary.HeapAnalyzer.checkForLeak(HeapAnalyzer.java:122)
    at com.squareup.leakcanary.internal.HeapAnalyzerService.onHandleIntent(HeapAnalyzerService.java:58)
    at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
    at android.os.Handler.dispatchMessage(Handler.java:102)
    at android.os.Looper.loop(Looper.java:135)
    at android.os.HandlerThread.run(HandlerThread.java:61)

  • Reference Key: d2a65a86-747a-4766-ae1a-650984bd2396

  • Device: LGE google Nexus 4 occam

  • Android Version: 5.1.1 API: 22 LeakCanary: 1.5 00f37f5

  • Durations: watch=350620ms, gc=358ms, heap dump=9304ms, analysis=146973ms

  • Excluded Refs:
    | Field: android.view.inputmethod.InputMethodManager.mNextServedView
    | Field: android.view.inputmethod.InputMethodManager.mServedView
    | Field: android.view.inputmethod.InputMethodManager.mServedInputConnection
    | Field: android.view.inputmethod.InputMethodManager.mCurRootView
    | Field: android.animation.LayoutTransition$1.val$parent
    | Field: android.view.textservice.SpellCheckerSession$1.this$0
    | Field: android.support.v7.internal.widget.ActivityChooserModel.mActivityChoserModelPolicy
    | Field: android.widget.ActivityChooserModel.mActivityChoserModelPolicy
    | Field: android.accounts.AccountManager$AmsTask$Response.this$1
    | Field: android.media.MediaScannerConnection.mContext
    | Field: android.os.UserManager.mContext
    | Field: android.media.AudioManager$1.this$0
    | Field: android.widget.Editor$Blink.this$0
    | Field: android.net.ConnectivityManager.sInstance
    | Field: android.view.Choreographer$FrameDisplayEventReceiver.mMessageQueue (always)
    | Static field: android.text.TextLine.sCached
    | Thread:FinalizerWatchdogDaemon (always)
    | Thread:main (always)
    | Thread:LeakCanary-Heap-Dump (always)
    | Class:java.lang.ref.WeakReference (always)
    | Class:java.lang.ref.SoftReference (always)
    | Class:java.lang.ref.PhantomReference (always)
    | Class:java.lang.ref.Finalizer (always)
    | Class:java.lang.ref.FinalizerReference (always)

@ggaier
Copy link

ggaier commented Nov 18, 2016

I have the same error too.

@AAverin
Copy link

AAverin commented Nov 18, 2016

Looks like we also have it on Samsung Galaxy S6 Edge, at least

@hidetag
Copy link

hidetag commented Nov 20, 2016

In io.xujiaji.hnbc:1.0:1.

  • FAILURE in 1.5 00f37f5:java.lang.OutOfMemoryError: OutOfMemoryError thrown while trying to throw OutOfMemoryError; no stack available
  • Reference Key: 7a252a3c-13db-4926-a3a3-1e6418fa1593
  • Device: Xiaomi Xiaomi 2014813 2014813
  • Android Version: 5.1.1 API: 22 LeakCanary: 1.5 00f37f5
  • Durations: watch=5014ms, gc=182ms, heap dump=2945ms, analysis=25438ms
  • Excluded Refs:
    | Field: android.view.inputmethod.InputMethodManager.mNextServedView
    | Field: android.view.inputmethod.InputMethodManager.mServedView
    | Field: android.view.inputmethod.InputMethodManager.mServedInputConnection
    | Field: android.view.inputmethod.InputMethodManager.mCurRootView
    | Field: android.animation.LayoutTransition$1.val$parent
    | Field: android.view.textservice.SpellCheckerSession$1.this$0
    | Field: android.support.v7.internal.widget.ActivityChooserModel.mActivityChoserModelPolicy
    | Field: android.widget.ActivityChooserModel.mActivityChoserModelPolicy
    | Field: android.accounts.AccountManager$AmsTask$Response.this$1
    | Field: android.media.MediaScannerConnection.mContext
    | Field: android.os.UserManager.mContext
    | Field: android.media.AudioManager$1.this$0
    | Field: android.widget.Editor$Blink.this$0
    | Field: android.net.ConnectivityManager.sInstance
    | Field: android.view.Choreographer$FrameDisplayEventReceiver.mMessageQueue (always)
    | Static field: android.text.TextLine.sCached
    | Thread:FinalizerWatchdogDaemon (always)
    | Thread:main (always)
    | Thread:LeakCanary-Heap-Dump (always)
    | Class:java.lang.ref.WeakReference (always)
    | Class:java.lang.ref.SoftReference (always)
    | Class:java.lang.ref.PhantomReference (always)
    | Class:java.lang.ref.Finalizer (always)
    | Class:java.lang.ref.FinalizerReference (always)

@AAverin
Copy link

AAverin commented Nov 23, 2016

@pyricau mentioning you here because you opened the original #223 story

Is #223 back again?
We have this issue on all Samsungs, unable to parse the dump.

@MerlinYu
Copy link

@AAverin Recently I found this leak on my Samsung Galaxy Note3,what cause it ?

@AAverin
Copy link

AAverin commented Nov 30, 2016

@MerlinYu I think it's just LeakCanary failing to parse heap for any leak. So any leak in your app could cause this OutOfMemory issue present on debug builds

@mjblackhorse
Copy link

I have the same problem on Emulator

@JakeWharton
Copy link
Collaborator

Thanks for the report. All OOMs during analysis are being tracked as #484 since they all have the same root cause: using too much memory for analysis. #456 is also related.

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

7 participants