Summary: | Firefox (and other apps) strobe on resize - failed repaint? | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | zacharytalis |
Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 5.25.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | STROBE WARNING - Firefox flicker |
Description
zacharytalis
2022-06-20 20:16:19 UTC
Created attachment 149965 [details]
STROBE WARNING - Firefox flicker
It looks related to the opaque region hint. Alright, this is a Firefox bug after all. Firefox creates two surfaces - one with the drop shadow, and the other with web page contents. It sets opaque regions on both surfaces, it's worth noting that the drop shadow surface has a hollow/transparent part where web page should be. It appears like when resizing firefox, the web page surface can uncover those hollow parts. Since firefox says that the hollow part is opaque, kwin won't try to repaint the area below it and you will see artifacts as in the video. Why did it show up in 5.25? We made kwin use opaque region hints more "aggressively" in order to avoid repainting screen areas that are covered by opaque regions. So if you scroll a web page in firefox and firefox is the top most window, kwin should try to repaint firefox and nothing more. That being said, this is a firefox bug. It should either ensure that web page surface always covers that hollow area (it would be the best solution as it is going to make window resizing more pleasant) or not set an opaque region in the drop shadow surface. I will file a bug report in bugzilla.mozilla.org if it's not already and link it here. Oh, nvm, I'm on wayland and you're on X11. This should be fixed in 5.25.1 *** This bug has been marked as a duplicate of bug 455617 *** (In reply to Vlad Zahorodnii from comment #4) > Oh, nvm, I'm on wayland and you're on X11. This should be fixed in 5.25.1 > > *** This bug has been marked as a duplicate of bug 455617 *** Thank youuuu <3 |