https://bugs.kde.org/show_bug.cgi?id=458771
--- Comment #4 from p...@pfortin.com --- I've been working with shotcut (video editor); the flickering started affecting various regions of that window. After window shading and restoring the window, I noticed something new/strange: keystrokes were totally ignored (space for start/stop playing, etc.) Then, the entire window started to window-shade on/off on its own. Each on/off appeared synchronized with clock updates -- each second (sometimes 2 seconds), the window would be window-shaded, then restored, etc. Very slow flickering. Referring back to my "container" comments, it appears various containers (within a window (areas of the window), and the entire window) flicker independently. There is no consistency in the speed of flicker -- milliseconds for some flickering; now, on/off cycles in seconds for the entire window. Other window/applications are not affected. It's been suggested that this could be a screen issue -- I consider this premise impossible because physical monitors are only aware of video streams as pixels; they have no concept of display areas varying in size from a few pixels flickering to entire application windows flickering. When flickering starts, an application can also appear visually frozen. Moving the window as little as one pixel refreshes the window into the view it should have; but it instantly appears frozen again. Sigh... so many symptoms... though they appear "container" related. Like updating a window area, or an entire window, and anything in between... Is there some common code that handles painting all areas regardless of size? This is beginning to feel like a memory leak or heap overflow. I'm mainly a user who writes python code; not a system developer. -- You are receiving this mail because: You are watching all bug changes.
