Open jleibs opened 5 months ago
Note: can't repro on 0.12.0 so suspect this is related to the the egui / wgpu update rather than another regression in chrome itself.
Bisection:
Also worth noting, forcing renderer=webgl
doesn't resolve the issue. So it's not related to the try-then-fallback logic.
Another observation: (1) This is very reminiscent of https://github.com/rerun-io/rerun/issues/3931 (2) During the range where we weren't able to test on chrome we added https://github.com/rerun-io/rerun/pull/4877 which added just a bit more code to: https://github.com/oxkitsune/rerun/blob/3f787b44ebb4a566224aba821024b27214245575/crates/re_renderer/shader/rectangle_fs.wgsl#L6-L9 which was warned against.
Confirmed: reverting https://github.com/rerun-io/rerun/pull/4877 remedies the problem.
Weird that "Unable to create texture object" is the error message for having a too large shader O.o
We should open an issue on wgpu
about removing that unwrap
though
@jleibs this got fixed by now?
Most often happens after clicking to load the structure-from-motion example.
Sometimes it works.
Sometimes I get:
Sometimes chrome itself completely hangs and needs to be killed.
Additional details
OS Version: Ubuntu 22.10 (Sway / Wayland) Browser: Google Chrome Version 120.0.6099.199 (Official Build) (64-bit)
Console log from when it crashes