Repository navigation
Engine crashes #6503
Copy link
Copy link
Closed
Labels
c: crashStack traces logged to the consoleStack traces logged to the consoleengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.
Description
I've been getting a lot of engine crashes today. I ran with a debug engine but that didn't get me a stack trace. Here's one example of the logs around a crash. At the time, I was on the gallery's progress indicator page, poking at it with the Observatory.
10-24 16:09:30.358 15164 15185 F libc : Fatal signal 11 (SIGSEGV), code 2, fault addr 0x82b41e60 in tid 15185 (Thread-4)
10-24 16:09:30.360 271 271 W : debuggerd: handling request: pid=15164 uid=10112 gid=10112 tid=15185
10-24 16:09:30.378 15502 15502 E : debuggerd: process stopped due to unexpected signal 27
10-24 16:09:30.408 271 271 W : debuggerd: resuming target 15164
10-24 16:09:30.409 2231 15503 W ActivityManager: Force finishing activity io.flutter.examples.gallery/org.domokit.sky.shell.SkyActivity
10-24 16:09:30.432 295 295 E lowmemorykiller: Error writing /proc/15164/oom_score_adj; errno=22
10-24 16:09:30.471 2231 2870 W InputDispatcher: channel '20eb12d io.flutter.examples.gallery/org.domokit.sky.shell.SkyActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9
10-24 16:09:30.471 2231 2870 E InputDispatcher: channel '20eb12d io.flutter.examples.gallery/org.domokit.sky.shell.SkyActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
10-24 16:09:30.476 2231 8212 D GraphicsStats: Buffer count: 4
10-24 16:09:30.476 2231 26028 I ActivityManager: Process io.flutter.examples.gallery (pid 15164) has died
10-24 16:09:30.476 2231 26028 D ActivityManager: cleanUpApplicationRecord -- 15164
10-24 16:09:30.485 2231 3156 I OpenGLRenderer: Initialized EGL, version 1.4
10-24 16:09:30.485 2231 3156 D OpenGLRenderer: Swap behavior 1
10-24 16:09:30.486 2231 8212 I WindowManager: WIN DEATH: Window{20eb12d u0 io.flutter.examples.gallery/org.domokit.sky.shell.SkyActivity}
10-24 16:09:30.486 2231 8212 W InputDispatcher: Attempted to unregister already unregistered input channel '20eb12d io.flutter.examples.gallery/org.domokit.sky.shell.SkyActivity (server)'
10-24 16:09:30.486 2231 8212 W WindowManager: Force-removing child win Window{a41679b u0 SurfaceView - io.flutter.examples.gallery/org.domokit.sky.shell.SkyActivity} from container Window{20eb12d u0 io.flutter.examples.gallery/org.domokit.sky.shell.SkyActivity}
10-24 16:09:30.486 2231 8212 I WindowManager: Destroying surface Surface(name=SurfaceView - io.flutter.examples.gallery/org.domokit.sky.shell.SkyActivity) called by com.android.server.wm.WindowStateAnimator.destroySurface:2014 com.android.server.wm.WindowStateAnimator.destroySurfaceLocked:881 com.android.server.wm.WindowState.removeLocked:1449 com.android.server.wm.WindowManagerService.removeWindowInnerLocked:2478 com.android.server.wm.WindowManagerService.removeWindowInnerLocked:2457 com.android.server.wm.WindowManagerService.removeWindowLocked:2436 com.android.server.wm.WindowState$DeathRecipient.binderDied:1780 android.os.BinderProxy.sendDeathNotice:688
10-24 16:09:30.490 2231 8212 I WindowManager: Destroying surface Surface(name=io.flutter.examples.gallery/org.domokit.sky.shell.SkyActivity) called by com.android.server.wm.WindowStateAnimator.destroySurface:2014 com.android.server.wm.WindowStateAnimator.destroySurfaceLocked:881 com.android.server.wm.WindowState.removeLocked:1449 com.android.server.wm.WindowManagerService.removeWindowInnerLocked:2478 com.android.server.wm.WindowManagerService.removeWindowLocked:2436 com.android.server.wm.WindowState$DeathRecipient.binderDied:1780 android.os.BinderProxy.sendDeathNotice:688 <bottom of call stack>
10-24 16:09:30.496 2231 31778 W WindowManager: Failed looking up window
10-24 16:09:30.496 2231 31778 W WindowManager: java.lang.IllegalArgumentException: Requested window android.os.BinderProxy@b5662 does not exist
10-24 16:09:30.496 2231 31778 W WindowManager: at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:9100)
10-24 16:09:30.496 2231 31778 W WindowManager: at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:9091)
10-24 16:09:30.496 2231 31778 W WindowManager: at com.android.server.wm.WindowState$DeathRecipient.binderDied(WindowState.java:1777)
10-24 16:09:30.496 2231 31778 W WindowManager: at android.os.BinderProxy.sendDeathNotice(Binder.java:688)
10-24 16:09:30.496 2231 31778 I WindowManager: WIN DEATH: null
10-24 16:09:31.137 3884 4056 W OpenGLRenderer: Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
c: crashStack traces logged to the consoleStack traces logged to the consoleengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.
Activity
Hixie commentedon Oct 24, 2016
Hixie commentedon Oct 24, 2016
eseidelGoogle commentedon Oct 25, 2016
Do you have a tombstone file by chance? @chinmaygarde or @jason-simmons
might recognize the failure from logs.
On Mon, Oct 24, 2016 at 4:39 PM, Ian Hickson [email protected]
wrote:
chinmaygarde commentedon Oct 25, 2016
Theory: The application is running out of memory.
Reasoning:
lowmemorykilleris attempting to first modify/proc/<pid>/oom_score_adjto see if the process is a candidate for lowering the priority for termination under memory stress. That presumably fails because there is nothing special about this process. Notice the PIDs match in all log instances.SIGTERM/SIGKILL, the issue is likely there was spike in memory stress that cause an allocation failure. Most software doesn't check for this and subsequently tried to dereference theNULLallocation causing the issue you see.Possible Causes:
More Investigation:
jason-simmons commentedon Oct 25, 2016
The third trace looks like a null pointer dereference - possibly similar to #6025?
Hixie commentedon Oct 25, 2016
I was suspicious of a memory leak issue because I had caused one of those myself earlier, and so on several occasions I was actually staring at the Dart heap data when it crashed and the heap was < 50MB.
Hixie commentedon Oct 25, 2016
(How do I get a tombstone file?)
chinmaygarde commentedon Oct 25, 2016
I haven't used those for diagnosing issues. @eseidel, @jason-simmons ?
eseidelGoogle commentedon Oct 25, 2016
Typically
adb pull /data/tombstones/tombstone_01etc should pull one. But normally when they're written it says so in theadb logcatto tell you to go looking. :)chinmaygarde commentedon Oct 25, 2016
I was wrong about the
lowmemorykillermessage. That seems to always be present irrespective of the type of crash.eseidelGoogle commentedon Feb 17, 2017
I don't think there is anything to do with this bug anymore? Please re-open if you disagree.
github-actions commentedon Sep 5, 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 -vand a minimal reproduction of the issue.