Summary: | System Monitor crashes in ToolBarLayoutDelegate::ensureItemVisibility() when going from Overview > Processes > back to Overview and then closing | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kirigami | Reporter: | guimarcalsilva |
Component: | general | Assignee: | Marco Martin <notmart> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | 288pat0tem, ahiemstra, biladina102, domy.os+kde, dva.lider, emaster987, gabravier, GeoBaltz, ja.vo, kde, kde, liubomirwm, nate, plasma-bugs, robertdevasia64, sahincapiec, saivinob, shostak93, stefanomilani92, wl |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.81.0 | ||
Target Milestone: | Not decided | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/frameworks/kirigami/commit/05b5a1b2fa3552f67e9e4d0a144381438b7458c0 | Version Fixed In: | Frameworks 5.83 with Plasma 5.22 |
Sentry Crash Report: | |||
Attachments: | Valgrind log - compressed |
Description
guimarcalsilva
2021-05-06 20:32:52 UTC
Running it from the terminal shows this when it crashes: QProcess: Destroyed while process ("/usr/lib/x86_64-linux-gnu/libexec/ksysguard/ksgrd_network_helper") is still running. org.kde.ksysguard.plugin.network: Helper process terminated abnormally! org.kde.ksysguard.plugin.network: "" QProcess: Destroyed while process ("/usr/lib/x86_64-linux-gnu/libexec/ksysguard/ksgrd_network_helper") is still running. org.kde.ksysguard.plugin.network: Helper process terminated abnormally! org.kde.ksysguard.plugin.network: "" KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = plasma-systemmonitor path = /usr/bin pid = 9258 KCrash: Arguments: /usr/bin/plasma-systemmonitor KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 15 and type 'Read', disabling... [2]+ Parado plasma-systemmonitor Created attachment 138203 [details]
Valgrind log - compressed
Log with Valgrind. I don't know if this can be useful or not.
crashing in kirigami *** Bug 436807 has been marked as a duplicate of this bug. *** *** Bug 436869 has been marked as a duplicate of this bug. *** >Log with Valgrind. I don't know if this can be useful or not.
valgrind logs are always useful, there's quite a few mistakes shown up there.
I can't see the crash though. Do you remember if it crashed whilst you were recording in valgrind?
From line 3000 the program is exiting and there's nothing that matches up with the gdb trace.
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kirigami/-/merge_requests/289 Git commit 05b5a1b2fa3552f67e9e4d0a144381438b7458c0 by David Redondo. Committed on 11/05/2021 at 07:28. Pushed by davidre into branch 'master'. Disconnect before destroying items Destroying them causes us to get a visibleChanged signal M +2 -0 src/toolbarlayoutdelegate.cpp https://invent.kde.org/frameworks/kirigami/commit/05b5a1b2fa3552f67e9e4d0a144381438b7458c0 *** Bug 437426 has been marked as a duplicate of this bug. *** *** Bug 437480 has been marked as a duplicate of this bug. *** *** Bug 437651 has been marked as a duplicate of this bug. *** *** Bug 437729 has been marked as a duplicate of this bug. *** *** Bug 437741 has been marked as a duplicate of this bug. *** *** Bug 437785 has been marked as a duplicate of this bug. *** *** Bug 437983 has been marked as a duplicate of this bug. *** *** Bug 437786 has been marked as a duplicate of this bug. *** *** Bug 438050 has been marked as a duplicate of this bug. *** *** Bug 438091 has been marked as a duplicate of this bug. *** *** Bug 438276 has been marked as a duplicate of this bug. *** *** Bug 438339 has been marked as a duplicate of this bug. *** *** Bug 438560 has been marked as a duplicate of this bug. *** *** Bug 438759 has been marked as a duplicate of this bug. *** *** Bug 439114 has been marked as a duplicate of this bug. *** |