Skip to content

closing 'flutter run' causes an exception on an Android device. #7414

Closed

Description

@apwilson
No description provided.

Activity

  1. apwilson commented on Jan 10, 2017

    @apwilson
    ContributorAuthor
    01-10 09:58:26.149 21256 21274 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 21274 (Thread-2)
    01-10 09:58:26.149   167   167 W         : debuggerd: handling request: pid=21256 uid=10115 gid=10115 tid=21274
    01-10 09:58:26.180 21308 21308 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    01-10 09:58:26.180 21308 21308 F DEBUG   : Build fingerprint: 'google/ryu/dragon:7.0/NRD90R/3141966:userdebug/dev-keys'
    01-10 09:58:26.180 21308 21308 F DEBUG   : Revision: '0'
    01-10 09:58:26.180 21308 21308 F DEBUG   : ABI: 'arm'
    01-10 09:58:26.180 21308 21308 F DEBUG   : pid: 21256, tid: 21274, name: Thread-2  >>> com.google.fuchsia.armadillo <<<
    01-10 09:58:26.180 21308 21308 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
    01-10 09:58:26.180 21308 21308 F DEBUG   :     r0 00000000  r1 df742d85  r2 dfbf99fc  r3 71b45033
    01-10 09:58:26.180 21308 21308 F DEBUG   :     r4 d0546028  r5 d0546000  r6 d0bc2840  r7 ee70e008
    01-10 09:58:26.180 21308 21308 F DEBUG   :     r8 00000000  r9 00000004  sl e26375dc  fp dfbfcc90
    01-10 09:58:26.180 21308 21308 F DEBUG   :     ip dfbfcf14  sp e26374e0  lr df742d9f  pc dfd5cdfc  cpsr 480e0030
    01-10 09:58:26.183 21308 21308 F DEBUG   : 
    01-10 09:58:26.183 21308 21308 F DEBUG   : backtrace:
    01-10 09:58:26.183 21308 21308 F DEBUG   :     #00 pc 00006dfc  /vendor/lib/libnvglsi.so (_nv002glsi+23)
    01-10 09:58:26.183 21308 21308 F DEBUG   :     #01 pc 005c3d9b  /vendor/lib/libglcore.so
    01-10 09:58:26.183 21308 21308 F DEBUG   :     #02 pc 005b6c7b  /vendor/lib/libglcore.so
    01-10 09:58:26.183 21308 21308 F DEBUG   :     #03 pc 005b7bb5  /vendor/lib/libglcore.so
    01-10 09:58:26.183 21308 21308 F DEBUG   :     #04 pc 00631a2d  /vendor/lib/libglcore.so
    01-10 09:58:26.183 21308 21308 F DEBUG   :     #05 pc 00631c21  /vendor/lib/libglcore.so
    01-10 09:58:26.183 21308 21308 F DEBUG   :     #06 pc 0060e95b  /vendor/lib/libglcore.so
    01-10 09:58:26.183 21308 21308 F DEBUG   :     #07 pc 0060eb9d  /vendor/lib/libglcore.so
    01-10 09:58:26.184 21308 21308 F DEBUG   :     #08 pc 005d243b  /vendor/lib/libglcore.so
    01-10 09:58:26.184 21308 21308 F DEBUG   :     #09 pc 005c23f3  /vendor/lib/libglcore.so
    01-10 09:58:26.184 21308 21308 F DEBUG   :     #10 pc 00007261  /vendor/lib/egl/libGLESv2_tegra.so
    01-10 09:58:26.184 21308 21308 F DEBUG   :     #11 pc 0003e34d  /vendor/lib/egl/libEGL_tegra.so
    01-10 09:58:26.184 21308 21308 F DEBUG   :     #12 pc 0003e3db  /vendor/lib/egl/libEGL_tegra.so
    01-10 09:58:26.184 21308 21308 F DEBUG   :     #13 pc 0000d755  /vendor/lib/egl/libEGL_tegra.so
    01-10 09:58:26.184 21308 21308 F DEBUG   :     #14 pc 00046f30  /vendor/lib/egl/libEGL_tegra.so
    01-10 09:58:26.789   167   167 W         : debuggerd: resuming target 21256
    
    
  2. eseidelGoogle commented on Jan 10, 2017

    @eseidelGoogle
    Contributor

    @chinmaygarde would know. That crash stack is all in GL land.

  3. eseidelGoogle commented on Jan 10, 2017

    @eseidelGoogle
    Contributor

    It appears google/ryu/dragon is a pixel C.

  4. chinmaygarde commented on Jan 11, 2017

    @chinmaygarde
    Contributor

    Is this device specific? I have a Pixel C handy. Will try it myself.

  5. self-assigned this
    on Jan 11, 2017
  6. eseidelGoogle commented on Jan 11, 2017

    @eseidelGoogle
    Contributor

    @apwilson to confirm: you're ctrl-C'ing the flutter run process to see this? I would not expect that to cause a gpu crash.

    Also, this is a user-debug build so symbols should be available on the device, and we can adb pull the relevant libraries across. (If they're not on the device we can get them from build servers.)

  7. jason-simmons commented on Jan 12, 2017

    @jason-simmons
    Member

    I can reproduce this on a Pixel C.

    When you ctrl-C flutter_tools, the tool sends a service protocol request to an extension in the Flutter framework that calls exit(0). This doesn't cleanly shut down the engine and its dependencies such as OpenGL. But it will call atexit handlers and global destructors, and maybe one of these is crashing within this EGL/GLES implementation?

  8. removed their assignment
    on Jan 19, 2017
  9. added this to the milestone on Feb 27, 2017
  10. added
    engineflutter/engine related. See also e: labels.
    on May 23, 2017
  11. Hixie commented on Dec 12, 2017

    @Hixie
    Contributor

    @jason-simmons tells me this is obsolete.

  12. github-actions commented on Sep 4, 2021

    @github-actions

    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.

  13. locked as resolved and limited conversation to collaborators on Sep 4, 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: crashStack traces logged to the consoleengineflutter/engine related. See also e: labels.platform-androidAndroid applications specifically

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions