You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cargo run --release -p readme https://wpt.live/css/css-flexbox/flexbox-paint-ordering-002.xhtml
I'm not surprised that wgpu fails to allocate a buffer that's >1GB. The question is why Vello is trying to allocate such a big buffer. The scene is relatively simple, and I am only trying to render it at 800x600 resolution (the command above actually multiplies that by the system's scale factor, but this bug also reproduces with a hardcoded scale factor of 1).
This test is specifically testing overlapping content, so it may be that that's triggering the bug in Vello.
The text was updated successfully, but these errors were encountered:
Hmm, this is strange. The buffer specifically appears to be sized at exactly $$2^{34}$$ bytes (i.e. $$2^{32}$$ u32 words?)
Can you determine which buffer is being created? I don't have the bandwidth to prioritise this, but if you can work out where the number is coming from, that would be very helpful.
Getting the same in https://github.com/actuate-rs/actuate when painting using a non-trivial number of elements in the Scene. I'm also appending each "widget"'s Scene to its parent, so maybe combining Scenes is the issue?
Edit: Or just from overflowing the size of the surface region? 🤔
When trying to render https://wpt.live/css/css-flexbox/flexbox-paint-ordering-002.xhtml with Blitz (tested with Blitz commit d02253d), I am getting the following error:
Stack trace:
To reproduce, run:
I'm not surprised that wgpu fails to allocate a buffer that's >1GB. The question is why Vello is trying to allocate such a big buffer. The scene is relatively simple, and I am only trying to render it at 800x600 resolution (the command above actually multiplies that by the system's scale factor, but this bug also reproduces with a hardcoded scale factor of 1).
This test is specifically testing overlapping content, so it may be that that's triggering the bug in Vello.
The text was updated successfully, but these errors were encountered: