Midori exhibits damaged region rendering bug
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 3.2k
- Forks
- 111
- PR merge metrics
- No merged PRs in 30d
Description
The bug only occurs when more than one (XDG) Midori is launched at start:
Pernosco trace with one Midori (no bug): https://pernos.co/debug/ZRR6PPBbwP069PiTlEETjQ/index.html
Pernosco trace with one Midori + another app (bug): https://pernos.co/debug/iv3Xp7WX877jgXfj8DYUvw/index.html
The traces seem to indicate there aren't any XDG popups or WlrSurface subsurfaces in play. The only thing triggering a "damage everything" call is "handle_map".
I'm worried this a race condition in the way we trigger a "damage everything". A hack would be to make "damage everything" calls persist for 2 frames instead of 1, or at least whenever surfaces are first mapped? @KaneTW
Contributor guide
No contributing guide indexed for this repository
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
Start by reproducing the damaged-region rendering bug with more than one XDG Midori launched at startup, then compare the two Pernosco traces linked in the issue. Inspect the handle_map path and the calls that trigger “damage everything”; done means the multi-Midori scenario renders correctly without relying on an unverified fixed-frame workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- computer-graphics, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100