[plasmashell] [Bug 523835] New: Plasmashell Crash Triggered By Switching Tabs in System Monitor Widget Settings

[email protected] (Unknown) Tue, 04 Aug 2026 02:43:06 +0000
Newsgroups gmane.comp.kde.devel.bugs
Message-ID <[email protected]/>
https://bugs.kde.org/show_bug.cgi?id=523835

            Bug ID: 523835
           Summary: Plasmashell Crash Triggered By Switching Tabs in
                    System Monitor Widget Settings
    Classification: Plasma
           Product: plasmashell
      Version First 6.7.3
       Reported In:
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: generic-crash
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: 1.0

Application: plasmashell (6.7.3)

ApplicationNotResponding [ANR]: false
Qt Version: 6.11.1
Frameworks Version: 6.28.0
Operating System: Linux 7.1.5-201.fc44.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 44 (KDE Plasma Desktop Edition)"
DrKonqi: 6.7.3 [CoredumpBackend]

-- Information about the crash:
I was attempting to adjust some of the setting of one of the System Monitor
widgets on my desktop when I discovered a consistently replicable bug that
causes a Plasma Shell segfault crash.  

Steps to Replicate:
  1. Create a System Monitor widget, including the pre-configured one for CPU
  2. Secondary/right click on the widget > Configure System Monitor Sensor 
  3. Left click on any of the tabs on the left side, switching between
different pages, until a crash occurs

I have not identified a specific sequence of changing between tabs to be the
cause, though the amount of testing I've done on this issue is limited, and I
have not reviewed the crash logs. The number of switches of tabs to cause a
crash does seem to be somewhat inconsistent, though. 

This is also my first time using widget configuration at all on KDE (I've not
bothered to customize my desktop much until now, about 6 months after
installing Fedora KDE on this PC), so I am unsure when this regression
occurred.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  0x00007f9f1104d5b0 in QV4::MarkStack::drain (this=0x5575dba47e50,
deadline=...) at
/usr/src/debug/qt6-qtdeclarative-6.11.1-3.fc44.x86_64/src/qml/memory/qv4mm.cpp:1160
#7  0x00007f9f1104ecfa in QV4::GCStateMachine::transition (this=0x5575da888b60)
at
/usr/src/debug/qt6-qtdeclarative-6.11.1-3.fc44.x86_64/src/qml/memory/qv4mm.cpp:1593
#8  0x00007f9f110512d3 in QV4::GCStateMachine::step (this=<optimized out>) at
/usr/src/debug/qt6-qtdeclarative-6.11.1-3.fc44.x86_64/src/qml/memory/qv4mm_p.h:150
#9  QV4::MemoryManager::runGC (this=0x5575d61e83a0) at
/usr/src/debug/qt6-qtdeclarative-6.11.1-3.fc44.x86_64/src/qml/memory/qv4mm.cpp:1379
#10 QV4::MemoryManager::runGC (this=0x5575d61e83a0) at
/usr/src/debug/qt6-qtdeclarative-6.11.1-3.fc44.x86_64/src/qml/memory/qv4mm.cpp:1357
#11 0x00007f9f11053344 in QV4::MemoryManager::allocate (this=0x5575d61e83a0,
allocator=0x5575d61e83b0, size=128) at
/usr/src/debug/qt6-qtdeclarative-6.11.1-3.fc44.x86_64/src/qml/memory/qv4mm_p.h:471
#12 QV4::MemoryManager::allocData (this=0x5575d61e83a0, size=128) at
/usr/src/debug/qt6-qtdeclarative-6.11.1-3.fc44.x86_64/src/qml/memory/qv4mm.cpp:1082
#13 0x00007f9f110534a5 in QV4::MemoryManager::allocObjectWithMemberData
(this=this@entry=0x5575d61e83a0, vtable=vtable@entry=0x7f9f114cc9a0
<QV4::QQmlValueTypeWrapper::static_vtbl>, nMembers=<optimized out>) at
/usr/src/debug/qt6-qtdeclarative-6.11.1-3.fc44.x86_64/src/qml/memory/qv4mm.cpp:1094
#14 0x00007f9f1122e842 in
QV4::MemoryManager::allocateObject<QV4::QQmlValueTypeWrapper> (this=<optimized
out>, ic=<optimized out>) at
/usr/src/debug/qt6-qtdeclarative-6.11.1-3.fc44.x86_64/src/qml/qml/qqmlvaluetypewrapper_p.h:101
#15 QV4::MemoryManager::allocateObject<QV4::QQmlValueTypeWrapper>
(this=<optimized out>, ic=0x7f9d852eea60) at
/usr/src/debug/qt6-qtdeclarative-6.11.1-3.fc44.x86_64/src/qml/memory/qv4mm_p.h:332
#16 QV4::MemoryManager::allocateObject<QV4::QQmlValueTypeWrapper>
(this=<optimized out>) at
/usr/src/debug/qt6-qtdeclarative-6.11.1-3.fc44.x86_64/src/qml/memory/qv4mm_p.h:342
#17 QV4::MemoryManager::allocate<QV4::QQmlValueTypeWrapper, void const*&,
QMetaType&, QMetaObject const*&, QV4::Heap::Object*&, int&,
QFlags<QV4::Heap::ReferenceObject::Flag>&> (this=<optimized out>) at
/usr/src/debug/qt6-qtdeclarative-6.11.1-3.fc44.x86_64/src/qml/memory/qv4mm_p.h:375
#18 QV4::QQmlValueTypeWrapper::create (engine=engine@entry=0x7f9dcc337910,
data=data@entry=0x0, metaObject=0x7f9f11de1e60
<QQuickColorValueType::staticMetaObject>, type=...,
object=object@entry=0x7f9d50429f00, property=13, flags=...) at
/usr/src/debug/qt6-qtdeclarative-6.11.1-3.fc44.x86_64/src/qml/qml/qqmlvaluetypewrapper.cpp:188
#19 0x00007f9f10fcd113 in QV4::loadProperty (v4=0x7f9dcc337910,
wrapper=0x7f9d50429f00, object=0x5575dba31950, property=...) at
/usr/src/debug/qt6-qtdeclarative-6.11.1-3.fc44.x86_64/src/qml/qml/qqmlpropertydata_p.h:284
#20 0x00007f9f10fcfd67 in QV4::QObjectWrapper::getQmlProperty
(engine=engine@entry=0x7f9dcc337910, qmlContext=..., wrapper=0x7f9d50429f00,
object=<optimized out>, name=0x7f9d852eea50, flags=..., flags@entry=...,
hasProperty=0x0, property=0x0) at
/usr/src/debug/qt6-qtdeclarative-6.11.1-3.fc44.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:520
#21 0x00007f9f1122610e in QV4::QQmlTypeWrapper::virtualGet (m=0x7f9d852eea40,
id=..., receiver=0x7f9d852eea40, hasProperty=0x0) at
/usr/src/debug/qt6-qtdeclarative-6.11.1-3.fc44.x86_64/src/qml/qml/qqmltypewrapper_p.h:111


Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.