Renderer stops functioning under stress without generating error messages
- Dominant language
- Rust
- Stars
- 4.3k
- Forks
- 300
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 61
Description
I decided to stress-test Vello by modifying the with_winit example. Instead of just one tiger, I changed it to draw hundreds of animated tigers.
My branch with the modified test can be found here: https://github.com/beholdnec/vello/tree/stress-test
I found certain conditions where the renderer would simply stop generating frames. In my branch, 128 tigers are drawn.
- If I draw more than 130 tigers or so, the app displays a black screen. It still responds to user input and exits when I close the window.
- If I zoom in too far, the picture freezes. If I zoom out again, the picture starts moving again.
When the renderer stops functioning, no error messages are generated and the program doesn't crash. It responds to user input but doesn't generate video.
I am running on an RTX 4080 with 16GB of video memory. My theory is I've hit a memory limit. It would be helpful if Vello would report an error in this condition rather than failing silently.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by checking out the reporter's stress-test branch and reproducing the issue through the modified with_winit example with increasing tiger counts and zoom levels. Compare the behavior around 128–130 tigers and during zoom changes. Done means the renderer no longer fails silently under these conditions and reports an error when it cannot generate frames.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100