Bug 489148 - System Monitor crash when selecting applications in 'Applications' tab
Summary: System Monitor crash when selecting applications in 'Applications' tab
Status: RESOLVED DUPLICATE of bug 487850
Alias: None
Product: plasma-systemmonitor
Classification: Applications
Component: general (show other bugs)
Version: 6.1.0
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-06-25 00:00 UTC by Aidan Coombs
Modified: 2024-06-25 10:26 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (76.00 KB, text/plain)
2024-06-25 00:00 UTC, Aidan Coombs
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aidan Coombs 2024-06-25 00:00:41 UTC
Application: plasma-systemmonitor (6.1.0)

Qt Version: 6.7.1
Frameworks Version: 6.3.0
Operating System: Linux 6.9.5-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: Arch Linux
DrKonqi: 6.1.0 [CoredumpBackend]

-- Information about the crash:
A pretty key use case for System Monitor is identifying applications' CPU and RAM usage, and the Applications tab, present by default, groups processes by which desktop application they correspond to. I've been experiencing this bug since the upgrade to Plasma 6, at which time I also switched from using Plasma on Xorg to Wayland.

I want to check the RAM usage of the (official) Spotify desktop application, famous for using quite a bit, so I open up System Monitor and click the 'Applications' tab (set to load 'When needed', which I think is the default). I see it's using about 800 MiB, but I want to see more information, so I click on the 'Spotify' entry. System Monitor freezes for a second, then crashes. This happens often with other applications, not just Spotify, but it doesn't happen all the time and I don't know why.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  0x00007e0c41f8363f in QHashPrivate::iterator<QHashPrivate::Node<QModelIndex, QSortFilterProxyModelPrivate::Mapping*> >::node (this=<synthetic pointer>) at /usr/src/debug/qt6-base/qtbase/src/corelib/tools/qhash.h:788
#6  QHash<QModelIndex, QSortFilterProxyModelPrivate::Mapping*>::const_iterator::value (this=<synthetic pointer>) at /usr/src/debug/qt6-base/qtbase/src/corelib/tools/qhash.h:1154
#7  QSortFilterProxyModel::sibling (this=<optimized out>, row=4, column=0, idx=...) at /usr/src/debug/qt6-base/qtbase/src/corelib/itemmodels/qsortfilterproxymodel.cpp:2149
#8  0x00007e0c3405af55 in QModelIndex::siblingAtRow (this=0x5d356f45c360, arow=<optimized out>) at /usr/include/qt6/QtCore/qabstractitemmodel.h:490
#9  ItemBranchIndicators::paint (this=0x5d356fddfac0, painter=0x7e0c1f1ff6d8) at /usr/src/debug/qqc2-desktop-style/qqc2-desktop-style-6.3.0/plugin/itembranchindicators.cpp:87


Reported using DrKonqi
Comment 1 Aidan Coombs 2024-06-25 00:00:44 UTC
Created attachment 170937 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Geraldo Simião 2024-06-25 04:19:19 UTC
Sounds just like this other 6.0 bug here #479235 => https://bugs.kde.org/show_bug.cgi?id=479235
Comment 3 Arjen Hiemstra 2024-06-25 10:26:34 UTC
*** This bug has been marked as a duplicate of bug 487850 ***