-
Notifications
You must be signed in to change notification settings - Fork 27.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash in gfx::NativeViewGLSurfaceEGL::NativeViewGLSurfaceEGL during startup #123
Comments
Ok, yeah easily repeatable by spamming the "recent activities" button during startup. |
Maybe the ANativeWindow* died in between posting the On..Available task and it running? |
@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 |
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. |
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: @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.
|
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 |
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
The text was updated successfully, but these errors were encountered: