Manually linking related crashes

Joseph Martinez's Avatar

Joseph Martinez

16 Feb, 2017 05:56 PM

Very often, my app will have a bug that manifests itself in slightly different ways as slightly different crashes, which are tracked separately in HockeyApp. This is good that each variation of the crash is stored. But, when I'm tracking bugs, it makes the crash list very messy. As a developer, I can tell that several of the crashes are manifestations of the same bug, and I'd like to be able to manually group/link them.

I know that I could Delete, Resolve, or Ignore the extra ones, but the data in them is still useful, and I'd like to be able to see them all in one place.

is there anything I can do to help me here?

  1. Support Staff 1 Posted by Andreas Linde on 16 Feb, 2017 06:12 PM

    Andreas Linde's Avatar

    Hi Joseph,

    what you could do is add the links to the 'main crash group' in the related crash groups as part of the annotation. Maybe even add the links to the related ones in the annotation of the main crash group. Sadly that is the only quite manual way I can think of right now.

    Can you give me some examples for such crash groups and help me understand why they are about the same? Maybe there is a way for us to improve the grouping for those.

    Best,
    Andreas

  2. 2 Posted by Joseph Martinez on 16 Feb, 2017 09:34 PM

    Joseph Martinez's Avatar

    Sure. Here are several examples of OutOfMemory exceptions, caused by trying to load a very large Bitmap on Android (using Xamarin):

    ------------------------------------
    VMRuntime.newNonMovableArray
    java.lang.OutOfMemoryError: Failed to allocate a 3686412 byte allocation with 2472577 free bytes and 2MB until OOM
    ------------------------------------
    ExceptionDispatchInfo.Throw()
    android.runtime.JavaProxyThrowable: System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. ---> Java.Lang.OutOfMemoryError: Failed to allocate a 36000012 byte allocation with 11987636 free bytes and 11MB until OOM
    ------------------------------------
    ExceptionDispatchInfo.Throw()
    android.runtime.JavaProxyThrowable: System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. ---> Java.Lang.OutOfMemoryError: Exception of type 'Java.Lang.OutOfMemoryError' was thrown.
    ------------------------------------
    BitmapFactory.nativeDecodeByteArray
    java.lang.OutOfMemoryError
    ------------------------------------
    ExceptionDispatchInfo.Throw()
    android.runtime.JavaProxyThrowable: System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. ---> Java.Lang.OutOfMemoryError: Failed to allocate a 45549372 byte allocation with 16777152 free bytes and 32MB until OOM
    ------------------------------------
    ExceptionDispatchInfo.Throw()
    android.runtime.JavaProxyThrowable: System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. ---> Java.Lang.OutOfMemoryError: Failed to allocate a 1440012 byte allocation with 207352 free bytes and 202KB until OOM
    ------------------------------------
    
  3. Support Staff 3 Posted by Andreas Linde on 16 Feb, 2017 11:03 PM

    Andreas Linde's Avatar

    Thanks for the details, we'll look into it and will get back to you as soon as possible.

    Andreas

  4. Support Staff 4 Posted by Stefan Haubold on 27 Mar, 2017 09:26 AM

    Stefan Haubold's Avatar

    Hi Joseph,

    sorry this took a bit longer then expected but the changes are now on production. Can you have a look at new incoming crashes if they are grouped better?

    Let me know if it works.

    Stefan

  5. 5 Posted by Joseph Martinez on 27 Mar, 2017 04:49 PM

    Joseph Martinez's Avatar

    Thanks! It may take some time for some more crashes to come in.

    -Joe

  6. Support Staff 6 Posted by Shawn Dyas on 03 Apr, 2017 04:48 PM

    Shawn Dyas's Avatar

    Hi Joseph,

    We have noticed that we have not heard from you in a while. Please let us know if this issue is resolved, or if we may be of further assistance.

    Thanks,
    Shawn

  7. Shawn Dyas closed this discussion on 03 Apr, 2017 04:48 PM.

  8. Joseph Martinez re-opened this discussion on 09 Apr, 2017 09:40 PM

  9. 7 Posted by Joseph Martinez on 09 Apr, 2017 09:40 PM

    Joseph Martinez's Avatar

    Shawn,

    Here are a couple more examples that have recently occurred of the same
    crash being reported as two different crashes:

    ==================================
    *android.graphics.Canvas.throwIfCannotDraw*
    java.lang.RuntimeException: Canvas: trying to use a recycled bitmap
    android.graphics.Bitmap@16523298
    and
    *Canvas.throwIfCannotDraw*
    Java.Lang.RuntimeException: Canvas: trying to use a recycled bitmap
    android.graphics.Bitmap@16523298
    ===================================
    *android.app.ActivityThread$H.handleMessage*
    android.app.RemoteServiceException: Bad notification posted from package
    com.elephanigma.starmygrooves: Couldn't cache contentViews:
    package=com.elephanigma.starmygrooves

    and
    *ActivityThread$H.handleMessage*
    Java.Lang.RuntimeException: Bad notification posted from package
    com.elephanigma.starmygrooves: Couldn't cache contentViews:
    package=com.elephanigma.starmygrooves
    =====================================

    The first example (ThrowIfCannotDraw) last occurred on April 3rd. The other
    example (handleMessage) last occurred on April 8th.

    -Joe

  10. Stefan Haubold closed this discussion on 24 Jun, 2017 11:14 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac