https://bugs.kde.org/show_bug.cgi?id=522988
--- Comment #6 from Zamundaaa <[email protected]> --- (In reply to Bjorn from comment #5) > Regarding the new PID, after the GPU hang/engine reset, kwin_wayland > restarted with a different PID (from 3237 to 2964 in the journal), > suggesting a full compositor restart. Which GPU hang? And if there's a crash, we need a backtrace, not guesses. > Regarding Modifier 0x0, I was assuming that meant linear format with no > dmabuf zero-copy, but I may be wrong about that. Could you clarify what > Modifier 0x0 means in the PipeWire negotiation context, and whether the > current behavior is actually incorrect? 0 does mean linear, but dmabufs can be linear. > The main symptom I'm seeing is OBS > screen capture causing near-100% CPU usage on all 20 cores at any resolution > (only tested 1080p and 4K) Well, then mention that, instead of technical details you don't have the knowledge to interpret. Please attach the output of wayland-info and > journalctl --user-unit plasma-kwin_wayland --boot 0 -- You are receiving this mail because: You are watching all bug changes.
