Skip to content

flutter logs should notice when the engine crashes and output a symbolic stack trace #1016

Closed
Closed
flutter logs should notice when the engine crashes and output a symbolic stack trace#1016
Labels
c: new featureNothing broken; request for a new capabilitytoolAffects the "flutter" command-line tool. See also t: labels.

Description

@stevenroose
stevenroose
opened on Dec 22, 2015

I noticed that sometimes an app I have crashes, both using the flutter tool and when deloyed.

This is the produced error message: https://gist.github.com/stevenroose/f46a481a534eb3e6d652
I can't pull the tombstone, since adb says it doesnt exist.

Of course, I don't know if this is a Flutter bug or a bug in my app, no Dart stack trace is provided.

Activity

  1. eseidel commented on Dec 22, 2015

    @eseidel
    eseidel
    on Dec 22, 2015
    Contributor

    We can get symbols for the backtrace if we have your flutter version.

    Also I suspect you don't have a "user debug" build of Android, so adb root doesn't work? In which case i'm not sure how to pull tombstones, but the internet likely knows:
    https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#safe=off&q=how+to+pull+tombstone+android

  2. eseidel commented on Dec 22, 2015

    @eseidel
    eseidel
    on Dec 22, 2015
    Contributor

    Ideally flutter logs should know how to show you symbols for your backtraces, and probably should know how to pull tombstones if that's possible.

  3. stevenroose commented on Dec 23, 2015

    @stevenroose
    stevenroose
    on Dec 23, 2015
    Author
    $ flutter --version
Flutter
Repository: https://github.com/flutter/flutter.git
Branch: master
Revision: 884c8e9e3585a55f89c5d414010d3ebcbaf2f8c1 (3 days ago)
  4. Hixie
    changed the title [-]Crash during runtime[/-] [+]flutter logs should notice when the engine crashes and output a symbolic stack trace[/+] on Jan 7, 2016
  5. Hixie
    added
    affects: dev experience
    c: new featureNothing broken; request for a new capability
    toolAffects the "flutter" command-line tool. See also t: labels.
    on Jan 16, 2016
  6. Hixie
    added this to the milestone on Jan 16, 2016
  7. sethladd
    modified the milestones: Hackathon, on Jan 29, 2016

  8. eseidelGoogle commented on Feb 19, 2016

    @eseidelGoogle
    eseidelGoogle
    on Feb 19, 2016
    Contributor

    This hasn't come up in a long time (the engine doesn't crash much in my experiance). I suspect we can punt this a later milestone.

  9. sethladd
    modified the milestones: , Hackathon on Feb 19, 2016

  10. Hixie commented on Feb 20, 2016

    @Hixie
    Hixie
    on Feb 20, 2016
    Contributor

    It mostly doesn't happen much because the framework carefully walks around the landmines. But I agree it's not critical for the near future.

  11. Hixie
    modified the milestones: 2: Make Early Adopters happy, on Dec 23, 2016

  12. Hixie commented on Dec 23, 2016

    @Hixie
    Hixie
    on Dec 23, 2016
    Contributor

    We've started becoming much more crashy and we have no good way to handle crash reports from the wild so I'm upping this one's priority.

  13. eseidelGoogle commented on Dec 27, 2016

    @eseidelGoogle
    eseidelGoogle
    on Dec 27, 2016
    Contributor

    Current process is that folks find them, pull them with the respective tools (adb logcat or XCode's log viewer/Console.app) and file a bug. I've been slowly iterating on a process for symbolicating reports we get from the field: https://github.com/flutter/engine/wiki/Symbolicating-production-crash-stacks

  14. Hixie
    removed
    old label "dev experience" (tell Hixie today if you don't want this label deleted)
    on Jan 22, 2017
  15. abarth
    modified the milestones: 2: Make Early Adopters happy, on Jan 26, 2017

  16. Hixie commented on Jun 12, 2017

    @Hixie
    Hixie
    on Jun 12, 2017
    Contributor

    Really I wish that flutter run and flutter logs did the equivalent of:

    ~/Android/Sdk/platform-tools/adb logcat | ~/dev/engine/src/third_party/android_tools/ndk/ndk-stack -sym ~/dev/engine/src/out/android_debug_unopt/

  17. gspencergoog commented on Jul 20, 2018

    @gspencergoog
    gspencergoog
    on Jul 20, 2018
    Contributor

    Closing this because I think the intended solution is summed up well in #16765.

  18. gspencergoog
    closed this as completedon Jul 20, 2018

  19. github-actions commented on Aug 16, 2021

    @github-actions
    github-actionsbot
    on Aug 16, 2021

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  20. github-actions
    locked as resolved and limited conversation to collaborators on Aug 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    c: new featureNothing broken; request for a new capabilitytoolAffects the "flutter" command-line tool. See also t: labels.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions