-
Notifications
You must be signed in to change notification settings - Fork 47
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
Failure at runtime from version 2.8.0 onwards in release/profile mode #70
Comments
So rebuilding and using Weston as the compositor thankfully gives me an error message emitted from the embedder.
The key difference in the configurations listed above is the |
@Charlie9830 Thank you for reporting the issue. I confirmed that it will occur in profile/release mode. |
We've been using |
Just ran into the same issue when building for |
|
As a workaround, I tried to enable the compressed pointers feature in the flutter-engine but I get a segmentation fault error when I try to run it on the target. |
Currently, it seems to be supported in Android only. |
@HidenoriMatsubayashi any update on this? I don't understand the snapshot workaround |
I'm working on this. This issue will be fixed with next release version (2.10.1) |
Specs
Device: Rpi4
Build System: Yocto Dunfell
Note: I don't directly build the flutter-engine with Yocto myself, currently I build the flutter-elinux tools as native and use them to build my application within Yocto.
Runtime Mode: Wayland client with Cage as the compositor.
Problem
Since upgrading to version 2.8.0 and later. My application fails to start on device. Cage boots up successfully but then the flutter application itself seems to be immediately exiting. As far as I can tell it does not reach the
main()
function of the dart code. Reverting to 2.5.3 solves the issue.Unfortunately, as of yet I haven't been able to extract an error message, it may be that cage is eating the error messages emitted from the app.
I am going to rebuild with Weston as the compositor and see if the same issue occurs.
The text was updated successfully, but these errors were encountered: