-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
Wasm rendering totally broken in the weirdest way #3763
Comments
Signed-off-by: Alex Saveau <saveau.alexandre@gmail.com>
What GPU and what drivers? |
Just to be clear, it works totally fine when I run it for x86, things only break in Chrome. Here's the
|
Also, I disabled all my chrome flags (just to check) and the bug is still there. Is there any other info I can provide? |
The random color flickering and irrecoverable freezes don't seem to happen on the default allocator leading me to believe that The performance is still pretty bad on the default allocator because |
Wow, thank you for finding that! I used |
Closing since this is really a wee alloc issue. |
Bevy version
0.6.0
Operating system & version
PopOS 21.10, Chrome 99.0.4840.0
What you did
Run this project: https://github.com/SUPERCILEX/bevy-vs-pixi
Click to add some more rectangles which seems to trigger the issue sooner. Otherwise, wait long enough and rendering will break.
What you expected to happen
Correct rendering. Notice the random color flickering in the background. The frame rate also takes a sudden hit and sometimes the app irreparably freezes.
What actually happened
Video: https://youtu.be/Uu1tus3Rk3U
Note that this only happens in Wasm on the release profile.
Additional information
The text was updated successfully, but these errors were encountered: