Bug 436008

Summary: ksysguard segfaults when system is under high load
Product: [Unmaintained] ksysguard Reporter: nutdriver716
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash CC: plasma-bugs-null
Priority: NOR Keywords: drkonqi
Version First Reported In: 5.19.5   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description nutdriver716 2021-04-21 16:27:29 UTC
Application: ksysguard (5.19.5)

Qt Version: 5.14.2
Frameworks Version: 5.74.0
Operating System: Linux 5.8.0-50-generic x86_64
Windowing system: X11
Distribution: Ubuntu 20.10

-- Information about the crash:
- What I was doing when the application crashed: Running a Deja-Dup backup which caused system to max out on CPU.

- Unusual behavior I noticed: The system was extremely slow and so was KSysGuard when I tried to use it. Deja Dup had a low priority (as set by me).

The crash can be reproduced sometimes.

-- Backtrace:
Application: System Monitor (ksysguard), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f1499a436f8 in QWidget::sizePolicy (this=this@entry=0x556eb7804bb0) at kernel/qwidget.cpp:10072
#5  0x00007f1499b4f923 in QLabelPrivate::updateLabel (this=0x556eb7554850, this@entry=0x7ffc4d14f0b0) at widgets/qlabel.cpp:1132
#6  0x00007f1499b50f84 in QLabel::setText (this=0x556eb75eb520, text=...) at widgets/qlabel.cpp:326
#7  0x00007f149a8bd9db in TopLevel::answerReceived (this=0x556eb74f3230, id=<optimized out>, answerList=...) at ./gui/ksysguard.cpp:466
#8  0x00007f149a600122 in KSGRD::SensorAgent::processAnswer(char const*, int) () from /lib/x86_64-linux-gnu/libksgrd.so.9
#9  0x00007f149a606325 in ?? () from /lib/x86_64-linux-gnu/libksgrd.so.9
#10 0x00007f1498e142e6 in QtPrivate::QSlotObjectBase::call (a=0x7ffc4d14f3b0, r=0x556eb7631bf0, this=0x556eb7501200) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#11 doActivate<false> (sender=0x556eb75da1d0, signal_index=15, argv=argv@entry=0x7ffc4d14f3b0) at kernel/qobject.cpp:3870
#12 0x00007f1498e0e068 in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7f1499067de0 <QProcess::staticMetaObject>, local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7ffc4d14f3b0) at kernel/qobject.cpp:3930
#13 0x00007f1498d4b9c1 in QProcess::readyReadStandardOutput (this=<optimized out>, _t1=...) at .moc/moc_qprocess.cpp:367
#14 0x00007f1498d5111d in QProcessPrivate::tryReadFromChannel (this=0x556eb75364f0, channel=0x556eb7536600) at io/qprocess.cpp:1057
#15 0x00007f1498d51675 in QProcessPrivate::_q_canReadStandardError (this=<optimized out>) at io/qprocess.cpp:1084
#16 QProcess::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=0x7ffc4d14f560) at .moc/moc_qprocess.cpp:210
#17 0x00007f1498e14320 in doActivate<false> (sender=0x556eb7582470, signal_index=3, argv=argv@entry=0x7ffc4d14f560) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395
#18 0x00007f1498e0e068 in QMetaObject::activate (sender=sender@entry=0x556eb7582470, m=m@entry=0x7f149906a1c0 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc4d14f560) at kernel/qobject.cpp:3930
#19 0x00007f1498e178b5 in QSocketNotifier::activated (this=this@entry=0x556eb7582470, _t1=<optimized out>, _t2=...) at .moc/moc_qsocketnotifier.cpp:141
#20 0x00007f1498e17c51 in QSocketNotifier::event (this=0x556eb7582470, e=0x7ffc4d14f660) at kernel/qsocketnotifier.cpp:266
#21 0x00007f1499a1a013 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x556eb7582470, e=0x7ffc4d14f660) at kernel/qapplication.cpp:3685
#22 0x00007f1498dde1ca in QCoreApplication::notifyInternal2 (receiver=0x556eb7582470, event=0x7ffc4d14f660) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153
#23 0x00007f1498e36425 in socketNotifierSourceDispatch (source=0x556eb7156720) at kernel/qeventdispatcher_glib.cpp:107
#24 0x00007f149049162b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007f14904918d8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007f14904919a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007f1498e35843 in QEventDispatcherGlib::processEvents (this=0x556eb7169290, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#28 0x00007f1498ddca4b in QEventLoop::exec (this=this@entry=0x7ffc4d14f870, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136
#29 0x00007f1498de4fc6 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:118
#30 0x00007f149a8beaf3 in kdemain (argc=<optimized out>, argv=<optimized out>) at ./gui/ksysguard.cpp:627
#31 0x00007f149a68ecb2 in __libc_start_main (main=0x556eb6302060 <main>, argc=1, argv=0x7ffc4d14fa98, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc4d14fa88) at ../csu/libc-start.c:314
#32 0x0000556eb630209e in _start ()
[Inferior 1 (process 19288) detached]

The reporter indicates this bug may be a duplicate of or related to bug 434779, bug 428064.

Possible duplicates by query: bug 434779, bug 433838, bug 433733, bug 428064, bug 425064.

Reported using DrKonqi
Comment 1 Justin Zobel 2022-12-01 05:22:16 UTC
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you can reproduce the issue with a more recent software version?  
  
If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-12-16 05:15:25 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-12-31 05:25:30 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!