| Summary: | Crash when maximizing window | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Moritz <bixilon> |
| Component: | generic-crash | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | bixilon, kde, nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.2 | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/plasma/kwin/-/commit/5a9ada65ef4dc47373553a7ab54c73dcd0367777 | Version Fixed/Implemented In: | 6.4.0 |
| Sentry Crash Report: | |||
|
Description
Moritz
2024-10-13 15:38:15 UTC
>#9 0x00007fb2bdc22a50 in QWindowSystemInterface::flushWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt6Gui.so.6
This is silly. We need to not call the base implementation in our QPA window, it does something questionable. Qt doesn't in the X11 or wayland backends.
We just need a sync call to QWindowSystemInterface::handleExposeEvent(window(), rect); but one without the flush.
If I was fixing this myself, where would I start? Can you give me a tip? You said, it should not call the base implementaton, so simply remove the super call? (In reply to David Edmundson from comment #1) > >#9 0x00007fb2bdc22a50 in QWindowSystemInterface::flushWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt6Gui.so.6 > > This is silly. We need to not call the base implementation in our QPA > window, it does something questionable. Qt doesn't in the X11 or wayland > backends. > > We just need a sync call to > QWindowSystemInterface::handleExposeEvent(window(), rect); but one without > the flush. The relevant code is gone in 6.4. |