-
Notifications
You must be signed in to change notification settings - Fork 26.7k
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 flutter engine on macOS #148279
Comments
It seems to be this assert that is firing. It seems like, at least in production code, this shouldn't crash the app if it can't run since it otherwise just skips the code in the next line anyway? |
Labeling this for team's input / attention based on the crash report. |
So far I have not been able to reproduce this since upgrading to macOS 14.5. So it may be a bad interaction with the OS. |
We also experience this issue and can confirm that it depends on the macOS version. One of our machines with macOS 14.4 nearly always crashes upon starting the app (in release mode, debug mode seems to work), whereas on a machine with macOS 14.5, this does not occur. It is unclear which other macOS versions might be affected, but it seems like quite a serious issue. The issue only started occurring after upgrading to Flutter 3.22. |
Chromium has a similar gn flag to disable asserts in release builds: https://source.chromium.org/chromium/chromium/src/+/main:build/config/BUILD.gn;drc=9dab28144192cefadbb96b778ef866ea3deb74ff;l=148 Related: flutter/flutter#148279
Chromium has a similar gn flag to disable asserts in release builds: https://source.chromium.org/chromium/chromium/src/+/main:build/config/BUILD.gn;drc=9dab28144192cefadbb96b778ef866ea3deb74ff;l=148 Related: flutter/flutter#148279
I also only see this on release builds but have been experiencing it prior to Flutter 3.22. |
Chromium has a similar gn flag to disable asserts in release builds: https://source.chromium.org/chromium/chromium/src/+/main:build/config/BUILD.gn;drc=9dab28144192cefadbb96b778ef866ea3deb74ff;l=148 Related: flutter/flutter#148279
Steps to reproduce
Unfortunately I don't have a simple reproduction step for this. There seems to be some kind of race condition initializing the flutter engine. Once in every several starts my app will crash while trying to enable semantics in the engine. I've tried wrapping my entire widget tree in an
ExcludeSemantics
node but this doesn't seem to help.This is the last thing keeping me from releasing this app to production but so far I haven't been able to pin it down to any particular component or library.
A typical crash trace is as follows:
Expected results
The app shouldn't crash.
Actual results
The app crashes on startup before it becomes interactive.
Code sample
Code sample
Screenshots or Video
Screenshots / Video demonstration
[Upload media here]
Logs
Logs
[Paste your logs here]
Flutter Doctor output
Doctor output
The text was updated successfully, but these errors were encountered: