Demo segfaults on start up after FlutterEngineRun about flutter-app-demo HOT 5 CLOSED

I made a Dockerfile real quick to isolate the issue some more. I think the issue might be that my kernel is not compatible with the flutter library. I'll try to get my hands on a better test machine.

To use this Dockerfile you will need to change the paths for flutter-plugin and flutter-engine in Cargo.toml
https://gist.github.com/j4qfrost/67ba0ac97753e9a48b5f8ce946340498
docker run --net=host --env="DISPLAY" --volume="$HOME/.Xauthority:/root/.Xauthority:rw" --device=/dev/dri:/dev/dri flutter-app-demo

Update: downgraded the kernel to 4.18.12 with the same results.

from flutter-app-demo.

As a heads up, I was able to start up @999eagle 's okuna-desktop project with some asset bundling errors, So I don't really know where to look to move forward on this one. Could it possibly be a glfw compatibility issue?

from flutter-app-demo.

@j4qfrost the issue is probably an incompatible icudtl.dat file. I'll update the demo tomorrow. We now bundle icudtl.dat with our engine builds, so this issue shouldn't occur if you use cargo-flutter.

from flutter-app-demo.

Cool. Also have you guys kept track with this branch? https://github.com/cloudwebrtc/flutter-engine/tree/texture_glfw

Not sure if it would be a good idea to start switching over or plan to. The branch looks stable with some change requests, but I'm just a noob.

from flutter-app-demo.

Yeah, we still need macosx and windows support so that it's not a regression. If you have experience with macosx or windows and want to help out, that would be awesome.

from flutter-app-demo.