https://bugs.kde.org/show_bug.cgi?id=400499

--- Comment #3 from Matt Fagnani <matthew.fagn...@utoronto.ca> ---
Created attachment 116263
  --> https://bugs.kde.org/attachment.cgi?id=116263&action=edit
New crash information added by DrKonqi

ksysguard (5.14.3) using Qt 5.11.1

- What I was doing when the application crashed:
I closed ksysguard and drkonqi started. This crash occurred with ksysguard and
Plasma 5.14.3, KF5 5.52.0, Qt 5.11.1 in Fedora 29. 

The crashes might be due to a race condition where two parts of the program(s)
involved tried to free the same memory since this crash occurred <10% of times
I've shut down ksysguard recently and some of the previous ksysguard crashes
I've seen had similar traces with a segmentation fault in
QLabelPrivate::clearContents at widgets/qlabel.cpp:1302 which was delete
picture; as I reported at https://bugs.kde.org/show_bug.cgi?id=350140#c16

This crash was due to a segmentation fault at QLabelPrivate::clearContents() at
widgets/qlabel.cpp:1309 which appears to be delete pixmap; at
https://code.qt.io/cgit/qt/qtbase.git/tree/src/widgets/widgets/qlabel.cpp

-- Backtrace (Reduced):
#7  0xb684c3ad in QLabelPrivate::clearContents() (this=0xa92c58) at
widgets/qlabel.cpp:1309
#8  0xb684cfd5 in QLabel::setText(QString const&) (this=0x9e6430, text=...) at
widgets/qlabel.cpp:293
#9  0xb7e8d49c in TopLevel::answerReceived(int, QList<QByteArray> const&)
(this=0x9d3d70, id=1, answerList=...) at
/usr/src/debug/ksysguard-5.14.3-1.fc29.i386/gui/ksysguard.cpp:450
#10 0xb7503925 in KSGRD::SensorAgent::processAnswer(char const*, int)
(this=0xa13c20, buf=0xcb6c40 "38.532108\nksysguardd> 665552\nksysguardd>
616420\nksysguardd> 191488\nksysguardd> 2398204\nksysguardd>
227328\nksysguardd> 61.467888\nksysguardd> 191488\nksysguardd>
227328\nksysguardd> 0\nksysguardd> 0\nksysgu"..., buflen=495) at
/usr/src/debug/libksysguard-5.14.3-1.fc29.i386/ksgrd/SensorAgent.cpp:91
#11 0xb750ae8e in KSGRD::SensorShellAgent::msgRcvd() (this=0xa13c20) at
/usr/include/qt5/QtCore/qarraydata.h:206

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

Reply via email to