Summary: | KWin crash when KWin script handler for clientRemoved | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Gonzalo Peci <weedv2> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | plr.vincent, qq767026763 |
Priority: | NOR | Keywords: | drkonqi, triaged |
Version: | 5.12.3 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Gonzalo Peci
2018-03-27 13:35:26 UTC
Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug packages and attach a new backtrace Im on Arch, unfortunately for certain things that will mean manually compiling. Which packages would need to have debug symbols? Thanks from the backtrace it looks like KWin would be sufficient Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! Git commit 8af6d4f5dc74385a9d52820562162dc190f452ff by Vlad Zagorodniy. Committed on 26/11/2018 at 08:50. Pushed by vladz into branch 'master'. [x11] Emit clientRemoved after client was removed Summary: Currently, there is a guarantee that a client, which is about to be removed, is no longer in the stacking order(both in constrained and unconstrained) when Workspace::removeClient is called. However, because the client gets removed from m_allClients after clientRemoved is emitted, it can be re-inserted back into the stacking order. In general, the pattern is to do some work and then notify others about what you've done by emitting a signal. In the case of Workspace::removeClient, we emit clientRemoved way before the client actually gets removed. Related: bug 400854 Test Plan: * Enable the following script: ```lang=js workspace.clientAdded.connect(function (client) { if (client.skipTaskbar || client.modal || client.transient) { return; } workspace.desktops = workspace.desktops + 1; workspace.currentDesktop = workspace.desktops; client.desktop = workspace.currentDesktop; }); workspace.clientRemoved.connect(function (client) { if (client.skipTaskbar || client.modal || client.transient) { return; } workspace.desktops = workspace.desktops - 1; }); ``` * Open an app, close the app. Reviewers: #kwin, graesslin Reviewed By: #kwin, graesslin Subscribers: graesslin, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D17069 M +2 -2 workspace.cpp https://commits.kde.org/kwin/8af6d4f5dc74385a9d52820562162dc190f452ff *** Bug 402546 has been marked as a duplicate of this bug. *** (In reply to Vlad Zagorodniy from comment #6) > Git commit 8af6d4f5dc74385a9d52820562162dc190f452ff by Vlad Zagorodniy. > Committed on 26/11/2018 at 08:50. > Pushed by vladz into branch 'master'. > > [x11] Emit clientRemoved after client was removed > > Summary: > Currently, there is a guarantee that a client, which is about to be removed, > is no longer in the stacking order(both in constrained and unconstrained) > when Workspace::removeClient is called. However, because the client gets > removed from m_allClients after clientRemoved is emitted, it can be > re-inserted back into the stacking order. > > In general, the pattern is to do some work and then notify others about > what you've done by emitting a signal. In the case of > Workspace::removeClient, > we emit clientRemoved way before the client actually gets removed. > Related: bug 400854 > > Test Plan: > * Enable the following script: > > ```lang=js > workspace.clientAdded.connect(function (client) { > if (client.skipTaskbar || client.modal || client.transient) { > return; > } > workspace.desktops = workspace.desktops + 1; > workspace.currentDesktop = workspace.desktops; > client.desktop = workspace.currentDesktop; > }); > > workspace.clientRemoved.connect(function (client) { > if (client.skipTaskbar || client.modal || client.transient) { > return; > } > workspace.desktops = workspace.desktops - 1; > }); > ``` > > * Open an app, close the app. > > Reviewers: #kwin, graesslin > > Reviewed By: #kwin, graesslin > > Subscribers: graesslin, kwin > > Tags: #kwin > > Differential Revision: https://phabricator.kde.org/D17069 > > M +2 -2 workspace.cpp > > https://commits.kde.org/kwin/8af6d4f5dc74385a9d52820562162dc190f452ff Do you know if this will be included in 15.5? Amazing that this was fix by the way. Sorry I could not provide debug symbols. Yes, it will be included in 5.15. Created attachment 117784 [details]
New crash information added by DrKonqi
kwin_x11 (5.14.5) using Qt 5.12.0
- What I was doing when the application crashed:
I am just playing cs:go when press tab button
-- Backtrace (Reduced):
#6 0x0000000000000000 in ()
#7 0x00007fbd1da8abdd in KWin::Workspace::constrainedStackingOrder() () at /usr/lib/libkwin.so.5
#8 0x00007fbd1da8b429 in KWin::Workspace::updateStackingOrder(bool) () at /usr/lib/libkwin.so.5
#9 0x00007fbd1da8b801 in KWin::Workspace::blockStackingUpdates(bool) () at /usr/lib/libkwin.so.5
#10 0x00007fbd1da394c7 in KWin::Client::destroyClient() () at /usr/lib/libkwin.so.5
(In reply to qq767026763 from comment #10) > Created attachment 117784 [details] > New crash information added by DrKonqi > > kwin_x11 (5.14.5) using Qt 5.12.0 > > - What I was doing when the application crashed: > I am just playing cs:go when press tab button > > -- Backtrace (Reduced): > #6 0x0000000000000000 in () > #7 0x00007fbd1da8abdd in KWin::Workspace::constrainedStackingOrder() () at > /usr/lib/libkwin.so.5 > #8 0x00007fbd1da8b429 in KWin::Workspace::updateStackingOrder(bool) () at > /usr/lib/libkwin.so.5 > #9 0x00007fbd1da8b801 in KWin::Workspace::blockStackingUpdates(bool) () at > /usr/lib/libkwin.so.5 > #10 0x00007fbd1da394c7 in KWin::Client::destroyClient() () at > /usr/lib/libkwin.so.5 If you're able to reproduce the crash in 5.15, please file a new bug report. I'm still not quite sure whether I fixed the crash because it's hard to reproduce it. |