IssueTracker

Migrated from https://crbug.com/1190824

UserAgent: Mozilla/5.0 (X11; CrOS aarch64 13729.56.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.95 Safari/537.36
Platform: 89.0.4389.95 (Official Build) (32-bit)

Steps to reproduce the problem:
1. Download https://github.com/davidk/PrusaSlicer-ARM.AppImage/releases/download/version_2.3.0/PrusaSlicer-2.3.0-GTK2-arm64.AppImage
2. Run it.
3. Add a cube to the 3D scene using a context menu in the 3D scene (right mouse button).
4. Press Tab. This runs the slicing process.
5. Move the vertical slider to change the number of layers visualized.
6. Switch to another application, switch back to PrusaSlicer.

What is the expected behavior?
Application still runs.

What went wrong?
Application closes with:

prusa-slicer: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

or

./prusa-slicer
prusa-slicer: Fatal IO error 104 (Connection reset by peer) on X server :0.

Did this work before? N/A

Chrome version: 89.0.4389.95  Channel: stable
OS Version: 13729.56.0
Flash Version:

We develop PrusaSlicer. This issue does not happen on the other two chromebooks we have for testing.

This issue sounds a little bit like
https://bugs.chromium.org/p/chromium/issues/detail?id=920030&q=Fatal%20IO%20error%2011%20%28Resource%20temporarily%20unavailable%29%20on%20X%20server%20%3A0.&can=2

however we experience the issue using our GPU intensive application only. It may be an issue of the virgl OpenGL virtualization.

Please let us know how we can help with debugging, however we have difficulties to compile and debug on ARM chromebooks due to

https://bugs.chromium.org/p/chromium/issues/detail?id=1190038&q=virtual%20machine&can=2

We also tested with the current https://github.com/prusa3d/prusaslicer (compiled in https://en.wikipedia.org/wiki/UserLAnd_Technologies) Android Linux virtualization, where the Linux chroot container gets access to full 8GB of RAM. The results are the same.