Repository navigation
Crash in gfx::NativeViewGLSurfaceEGL::NativeViewGLSurfaceEGL during startup #123
Description
Activity
- addedc: crashStack traces logged to the consoleStack traces logged to the console
on Nov 9, 2015 Comment by eseidelGoogle
Friday Aug 07, 2015 at 21:24 GMT
Ok, yeah easily repeatable by spamming the "recent activities" button during startup.
Comment by jamesr
Monday Aug 10, 2015 at 19:23 GMT
Maybe the ANativeWindow* died in between posting the On..Available task and it running?
Comment by chinmaygarde
Tuesday Aug 11, 2015 at 19:28 GMT
@eseidelGoogle https://github.com/domokit/sky_engine/blob/master/sky/shell/android/platform_view_android.cc#L63 is passing the Rasterizer an unretained reference. If the last reference is released via
PlatformViewAndroid::ReleaseWindowbefore the the GPU thread is able to create the GLSurface from the same, you would get a crash. I suggest passing the widget as a weak reference and check for the validity of the same when the rasterizer gets the onAcceleratedWidgetAvailable.Comment by jamesr
Tuesday Aug 11, 2015 at 19:53 GMT
I'm not seeing anything related to Rasterizer at that line. Weak refs don't work cross thread, which I believe this is trying to do, so we probably need a mutex guarded pointer that we check itself.
- addedengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.
on Dec 16, 2015 - addedplatform-androidAndroid applications specificallyAndroid applications specifically
on May 13, 2016 I was able to repro a crash by spamming the recent activities button during launch of a JIT (--debug) built app on Android just now:
I/DEBUG ( 186): Abort message: '[FATAL:rasterizer_direct.cc(59)] Check failed: surface_. GLSurface required.@jason-simmons or @chinmaygarde would know.
The --release (aot) builds launch too fast to hit this.
I suspect this is long since fixed.
I got rid of gfx entirely.
On Wed, Jul 13, 2016 at 8:29 AM Eric Seidel [email protected]
wrote:I suspect this is long since fixed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#123 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AACsNbnXDU82xL8XshKRN-b75o2J9pS-ks5qVQRugaJpZM4Ge7vx
.- added a commit that references this issue
on Mar 21, 2019 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.- locked as resolved and limited conversation to collaborators
on Aug 17, 2021
Friday Aug 07, 2015 at 21:23 GMT
Originally opened as https://github.com/flutter/engine/issues/507
gpu_thread crash during startup.
I started fitness app via shelldb:
sky/tools/shelldb start out/android_Debug sky/packages/sky/example/fitness/lib/main.dart
And right as I was doing so, I hit the recent activity button on my Nexus 5 and attempted to close the Asteroids.apk which was running behind it. I think that caused it to lose its gl context at a bad time.
Not sure if this is repeatable or if we care, but here is a stack:
@chinmaygarde @abarth