rust-windowing / rust-windowing/winit
`EventLoop` gets hung up when flooded with many events.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 1.3k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 9
Description
Description
When flooding the EventLoop with about 12k user events on my system only about 10k will be emitted to the handler. When sending additional events the next event is emitted (not the one just sent). The EventLoop will stay in this state for the duration of the application.
See minimal example here: https://github.com/AustinJ235/winit-slap
Windows version
Microsoft Windows [Version 10.0.22631.4602]
Winit version
0.30.8
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Run the minimal example at https://github.com/AustinJ235/winit-slap on Windows 10.0.22631.4602 with winit 0.30.8 and reproduce the flood of about 12k user events; then trace EventLoop event delivery. Done means all flooded events reach the handler and subsequent events are delivered normally rather than remaining delayed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100