Bug 425054 - KWin crash when repeatedly triggering present windows hot corner
Summary: KWin crash when repeatedly triggering present windows hot corner
Status: RESOLVED DUPLICATE of bug 423319
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.19.2
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2020-08-05 20:39 UTC by Lucas Streanga
Modified: 2020-09-14 20:30 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (2.07 KB, text/plain)
2020-08-15 04:40 UTC, Daniel Stevenson
Details
New crash information added by DrKonqi (2.24 KB, text/plain)
2020-08-16 19:08 UTC, Roger
Details
New crash information added by DrKonqi (1.94 KB, text/plain)
2020-08-21 08:03 UTC, Yevhen Sayenko
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lucas Streanga 2020-08-05 20:39:50 UTC
Application: kwin_x11 (5.19.2)

Qt Version: 5.14.2
Frameworks Version: 5.72.0
Operating System: Linux 5.4.0-42-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.19

-- Information about the crash:
Repeatedly triggering a hot corner set to present windows - all desktops can cause a crash. Triggering the hot corner once or triggering the corner and then selecting a window never causes a crash - but triggering the corner and then triggering it again while the windows are still presented causes a crash frequently. KWin must then be manually restarted. If the crash happens multiple times, KWin will be turned off alltogether and the "Enable Kwin on Startup" setting must be re-enabled.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault

[KCrash Handler]
#4  0x000055cf837e43d0 in  ()
#5  0x00007f1c3c0cffca in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) (this=0x55cf8315c770, e=0x7f1c1c00f830) at ./events.cpp:240
#6  0x00007f1c3973f4df in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) (this=<optimized out>, eventType=..., message=message@entry=0x7f1c1c00f830, result=result@entry=0x7ffd5209ee98) at kernel/qabstracteventdispatcher.cpp:488
#7  0x00007f1c24f4dbac in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) (this=this@entry=0x55cf830b1d30, event=event@entry=0x7f1c1c00f830) at qxcbconnection.cpp:550
#8  0x00007f1c24f4e6d6 in QXcbConnection::processXcbEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x55cf830b1d30, flags=...) at qxcbconnection.cpp:1029
#9  0x00007f1c24f7332c in QXcbUnixEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x55cf830f6520, flags=...) at qxcbeventdispatcher.cpp:61
#10 0x00007f1c39740d2a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffd5209eff0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#11 0x00007f1c3974a4a0 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1383
#12 0x000055cf826ff3db in main(int, char**) (argc=<optimized out>, argv=0x7ffd5209f268) at ./main_x11.cpp:479

The reporter indicates this bug may be a duplicate of or related to bug 424752, bug 423319.

Possible duplicates by query: bug 424752, bug 423319, bug 422899, bug 422558, bug 422275.

Reported using DrKonqi
Comment 1 Iiari 2020-08-09 04:41:15 UTC
As I reported on a different bug, I'm experiencing the same thing.  Since 5.19.3 dropped on Manjaro as an update to 5.18 stable, I too am getting crashes with Present Windows being repeatedly activated by hot edges.  Usually it's when activating and then rapidly retriggering the same edge to deactivate the effect.  Upon deactivating Present Windows, I get no animation, return to the last active app to find the compositor has crashed.  Sometimes KWin will start itself, sometimes I need to manually turn it back on.
Comment 2 Daniel Stevenson 2020-08-15 04:40:26 UTC
Created attachment 130881 [details]
New crash information added by DrKonqi

kwin_x11 (5.19.4) using Qt 5.15.0

- What I was doing when the application crashed:

I was in the present windows dialog, which I had toggled several times in a row by accident.  Upon selecting an app (Flatpak version of Steam), KWin crashed, but was able to restart itself.

-- Backtrace (Reduced):
#5  0x00007f844e7c492c in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) (this=<optimized out>, e=0x7f84400ddbc0) at /usr/include/qt5/QtCore/qvector.h:1041
#6  0x00007f844d3bd167 in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) (this=<optimized out>, eventType=..., message=message@entry=0x7f84400ddbc0, result=result@entry=0x7ffc5f5977f8) at kernel/qabstracteventdispatcher.cpp:488
#7  0x00007f84476a2571 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) (this=this@entry=0x55d8be96e5d0, event=event@entry=0x7f84400ddbc0) at qxcbnativeinterface.h:101
#8  0x00007f84476a3a86 in QXcbConnection::processXcbEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x55d8be96e5d0, flags=...) at qxcbconnection.cpp:1003
#9  0x00007f84476c62fc in QXcbUnixEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x55d8bea852b0, flags=...) at qxcbeventdispatcher.cpp:61
Comment 3 Roger 2020-08-16 19:08:51 UTC
Created attachment 130917 [details]
New crash information added by DrKonqi

kwin_x11 (5.19.4) using Qt 5.15.0

- What I was doing when the application crashed:
Exactly the same as reported above: repeatedly triggering the "Present Windows - All Desktops" set on my top-lef hot corner causes the crash. It is always reproduceable, but the number of times I need to trigger the hot corner before it crashes varies, usually 2 or 4 times. It always happens when *returning* from the "Present Windows - All Desktops" screen, not entering.

-- Backtrace (Reduced):
#5  0x00007f1dd7ab292c in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) (this=<optimized out>, e=0x7f1dcc0104f0) at /usr/include/qt5/QtCore/qvector.h:1041
#6  0x00007f1dd66ab167 in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) (this=<optimized out>, eventType=..., message=message@entry=0x7f1dcc0104f0, result=result@entry=0x7ffcac84c888) at kernel/qabstracteventdispatcher.cpp:488
#7  0x00007f1dd09a0571 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) (this=this@entry=0x5557361a1660, event=event@entry=0x7f1dcc0104f0) at qxcbnativeinterface.h:101
#8  0x00007f1dd09a1a86 in QXcbConnection::processXcbEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x5557361a1660, flags=...) at qxcbconnection.cpp:1003
#9  0x00007f1dd09c42fc in QXcbUnixEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x555736254c90, flags=...) at qxcbeventdispatcher.cpp:61
Comment 4 Yevhen Sayenko 2020-08-21 08:03:09 UTC
Created attachment 131069 [details]
New crash information added by DrKonqi

kwin_x11 (5.19.4) using Qt 5.14.2

- What I was doing when the application crashed:

Trigerring "Present Windows - All Desktops" action using the left-top corner edge of the screen. After this when I try to select a window - sometimes it crashes. 
But when I try to trigger "Present Windows - All Desktops" action while it is already open, it crashes constantly.

-- Backtrace (Reduced):
#5  0x00007fc3a0df9e36 in KWin::Workspace::workspaceEvent (this=0x55c003c369c0, e=0x7fc394024c70) at ./x11eventfilter.h:51
#6  0x00007fc39f9b0bcf in QAbstractEventDispatcher::filterNativeEvent (this=<optimized out>, eventType=..., message=message@entry=0x7fc394024c70, result=result@entry=0x7ffd02f9a308) at kernel/qabstracteventdispatcher.cpp:488
#7  0x00007fc3994a3865 in QXcbConnection::handleXcbEvent (this=this@entry=0x55c003b0dce0, event=event@entry=0x7fc394024c70) at qxcbnativeinterface.h:101
#8  0x00007fc3994a45c6 in QXcbConnection::processXcbEvents (this=0x55c003b0dce0, flags=...) at qxcbconnection.cpp:1029
#9  0x00007fc3994cd8e0 in QXcbUnixEventDispatcher::processEvents (this=0x55c003b6d5a0, flags=...) at qxcbeventdispatcher.cpp:61
Comment 5 Iiari 2020-08-23 02:32:27 UTC
FWIW, while we wait for the problem to be solved, I've found that a setting a reactivation time of 450 ns or higher doesn't seem to have this problem.  Anything less than that and it's an issue.  Also, I booted a fresh Manjaro KDE download from the iso and the issue is there as well, so it's not something users have done...
Comment 6 Iiari 2020-08-24 21:53:32 UTC
Never mind, today the 450 ns reactivate was crashing left and right... Oh well.
Comment 7 Nate Graham 2020-09-14 20:30:08 UTC

*** This bug has been marked as a duplicate of bug 423319 ***