Application: plasmashell (6.2.1) ApplicationNotResponding [ANR]: false Qt Version: 6.8.0 Frameworks Version: 6.7.0 Operating System: Linux 6.11.4-arch2-1-ml x86_64 Windowing System: Wayland Distribution: Arch Linux DrKonqi: 6.2.1 [CoredumpBackend] -- Information about the crash: I added thermalmonitor widget to the panel, then opened its configuration window and clicked 'add sensor' button, then scrolled throught the list of sensors and plasma crashed. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 QV4::Value::as<QV4::QObjectWrapper> (this=0x768e87f95f88) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/memory/qv4heap_p.h:45 #6 QV4::Value::as<QV4::QObjectWrapper> (this=0x768e87f95f88) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/jsruntime/qv4value_p.h:151 #8 0x0000768ea065172d in QV4::GCStateMachine::transition (this=0x6043614daac0) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/memory/qv4mm.cpp:1495 #9 QV4::GCStateMachine::transition (this=0x6043614daac0) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/memory/qv4mm.cpp:1477 #10 0x0000768ea06611b7 in QV4::GCStateMachine::step (this=<optimized out>) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/memory/qv4mm_p.h:79 Reported using DrKonqi
Created attachment 175108 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
Searchable backtrace Thread 1 (Thread 0x768e98fa9a00 (LWP 1399)): [KCrash Handler] #5 QV4::Value::as<QV4::QObjectWrapper> (this=0x768e87f95f88) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/memory/qv4heap_p.h:45 #6 QV4::Value::as<QV4::QObjectWrapper> (this=0x768e87f95f88) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/jsruntime/qv4value_p.h:151 #7 QV4::(anonymous namespace)::markWeakValues (that=0x6043614daac0, stateData=std::variant [index 1] = {...}) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/memory/qv4mm.cpp:749 #8 0x0000768ea065172d in QV4::GCStateMachine::transition (this=0x6043614daac0) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/memory/qv4mm.cpp:1495 #9 QV4::GCStateMachine::transition (this=0x6043614daac0) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/memory/qv4mm.cpp:1477 #10 0x0000768ea06611b7 in QV4::GCStateMachine::step (this=<optimized out>) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/memory/qv4mm_p.h:79 #11 QV4::MemoryManager::runGC (this=0x6043613d5430) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/memory/qv4mm.cpp:1272 #12 0x0000768ea056878a in QV4::MemoryManager::runGC (this=0x6043613d5430) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/memory/qv4mm.cpp:1260 #13 QV4::MemoryManager::allocate (this=0x6043613d5430, allocator=0x6043613d5440, size=64) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/memory/qv4mm_p.h:386 #14 QV4::MemoryManager::allocString (this=0x6043613d5430, unmanagedSize=<optimized out>) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/memory/qv4mm.cpp:994 #15 QV4::MemoryManager::allocWithStringData<QV4::String, QString const&> (this=0x6043613d5430, unmanagedSize=<optimized out>, arg1=...) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/memory/qv4mm_p.h:274 #16 QV4::ExecutionEngine::newString (this=<optimized out>, s=...) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/jsruntime/qv4engine.cpp:938 #17 0x0000768ea05d3aec in operator()<QString> (__closure=<synthetic pointer>, v=...) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:155 #18 QV4::loadProperty (v4=<optimized out>, wrapper=<optimized out>, object=0x604368100be0, property=...) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:178 #19 0x0000768e418cd077 in ?? () #20 0x0000000000000000 in ?? ()
Trace starts off the same but is not identical to bug 495035 "Plasma Widget system monitor sensor crashes on edit" Also bug 495193, bug 495076, bug 492606
Thank you for the bug report. Based on the backtrace it seems the same as bug 492606. I'm marking this as a duplicate of that one. You can follow the progress of this issue in the other report. *** This bug has been marked as a duplicate of bug 492606 ***