-
Notifications
You must be signed in to change notification settings - Fork 28.6k
firebase_release_smoke_test crashing consistently on Engine roll attempts #74502
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
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@flutter-symbolizer-bot #74502 (comment) engine#7c19824c6d08bb8e3fc4217058178d42d451e26b android debug x86 |
crash from #74502 (comment) symbolized using symbols for
|
Based on the back trace it looks like the error message is relevant:
|
Based on the commits in that roll I will guess that this might be related to flutter/engine#23634 and assign @gaaclarke |
ummm, not easy to find. Is that test in https://github.com/FirebaseExtended/flutterfire? |
The easiest way to reproduce this is running an app on an Android API level 16 emulator. Apps previously would be unable to create graphics contexts and would fail to render on old emulators. But with the latest engine the app process is now segfaulting. The failing test is being run on a Firebase test lab by a LUCI recipe: The test runs the https://github.com/flutter/flutter/tree/master/dev/integration_tests/release_smoke_test app on an emulator. |
This can be fixed by patching flutter/engine@296902b#diff-dde92a82824b129292aacba507c9807c5614fa6529e581d36531877c0d8eba80R108 to:
|
This is no longer P0 since the revert landed and the engine rolled into the framework. I will also close this as it seems the root cause of the issue has been found and can be integrated into the re-land. |
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 |
Uh oh!
There was an error while loading. Please reload this page.
Starting with #74457
For example: https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20firebase_release_smoke_test/6528/overview
On "Nexus 5, Virtual, API Level 19"
Some logs from the run:
Crash log from the roll to 7c19824
The text was updated successfully, but these errors were encountered: