Bug 426695 - Network Speed System Monitor Widget "Particles Vortex" eats up 100% of Ram and Swap
Summary: Network Speed System Monitor Widget "Particles Vortex" eats up 100% of Ram an...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Monitor (show other bugs)
Version: 5.19.5
Platform: Arch Linux Linux
: NOR crash
Target Milestone: 1.0
Assignee: Marco Martin
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2020-09-18 18:00 UTC by Jason A. Zelek
Modified: 2022-11-05 05:09 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason A. Zelek 2020-09-18 18:00:49 UTC
Application: plasmashell (5.19.5)

Qt Version: 5.15.1
Frameworks Version: 5.74.0
Operating System: Linux 5.8.9-arch2-1 x86_64
Windowing system: X11
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:

I was trying to get the network speed widget to display text and selected "Particles Vortex" from the drop down menu in 'Display Styles". After hitting apply the line chart that I had dissapeared and nothing else loaded. After a few minutes the system came to a halt. I was ablt to open htop and watched plasmashell slowly consume all available memory (32gb) along with all available swap (also 32gb). Killing plasmashell causes it to release the memory. 

- Unusual behavior I noticed: All memory consumed. Happens right after login since the widget is loading at startup.

- Custom settings of the application: Selected Particle Vortex as the widget display style.

Happy to provide screen shots or any addi

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fd17e89402d in  () at /usr/lib/libQt5QuickParticles.so.5
#5  0x00007fd17e8b75b7 in  () at /usr/lib/libQt5QuickParticles.so.5
#6  0x00007fd17e8b5bc7 in QQuickParticleSystem::nextSystemIndex() () at /usr/lib/libQt5QuickParticles.so.5
#7  0x00007fd17e8b6009 in QQuickParticleSystem::newDatum(int, bool, int) () at /usr/lib/libQt5QuickParticles.so.5
#8  0x00007fd17e8ab938 in QQuickParticleEmitter::emitWindow(int) () at /usr/lib/libQt5QuickParticles.so.5
#9  0x00007fd17e8b571d in  () at /usr/lib/libQt5QuickParticles.so.5
#10 0x00007fd2197cfcd8 in QAbstractAnimation::setCurrentTime(int) () at /usr/lib/libQt5Core.so.5
#11 0x00007fd2197cfe19 in  () at /usr/lib/libQt5Core.so.5
#12 0x00007fd2197ce723 in QUnifiedTimer::updateAnimationTimers(long long) () at /usr/lib/libQt5Core.so.5
#13 0x00007fd2197d046f in QAnimationDriver::advanceAnimation(long long) () at /usr/lib/libQt5Core.so.5
#14 0x00007fd21b472208 in  () at /usr/lib/libQt5Quick.so.5
#15 0x00007fd21a4eb752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#16 0x00007fd2199cfcda in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#17 0x00007fd219a27cc5 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5
#18 0x00007fd219a285aa in  () at /usr/lib/libQt5Core.so.5
#19 0x00007fd217e4abfc in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#20 0x00007fd217e9c1f9 in  () at /usr/lib/libglib-2.0.so.0
#21 0x00007fd217e49421 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#22 0x00007fd219a28941 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#23 0x00007fd2199ce65c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#24 0x00007fd2199d6af4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#25 0x00005606c0216f5d in  ()
#26 0x00007fd21939c152 in __libc_start_main () at /usr/lib/libc.so.6
#27 0x00005606c021719e in _start ()
[Inferior 1 (process 2188) detached]

Reported using DrKonqi
Comment 1 Nate Graham 2020-09-18 20:56:51 UTC
lol
Comment 2 Justin Zobel 2022-10-06 06:36:26 UTC
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-10-21 05:01:18 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 4 Bug Janitor Service 2022-11-05 05:09:39 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!