Bug 439333

Summary: Infinite Notification Crash
Product: [Frameworks and Libraries] frameworks-knotifications Reporter: ralph.ocdol63
Component: generalAssignee: kdelibs bugs <kdelibs-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash CC: kdelibs-bugs-null, nate
Priority: NOR    
Version First Reported In: 5.82.0   
Target Milestone: ---   
Platform: Manjaro   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description ralph.ocdol63 2021-06-30 13:57:52 UTC
SUMMARY
This bug was triggered by KDE Connect when I was donwloading on my mobile device, the notification keeps sending a notification to KDE Connect thus triggering the notification again and again until my machine freezes as it uses more and more resources 'till max. Although it can be caused by KDE Connect, not having a limiter or something on notification can be dangerous on its own, imagine a malicious application finds its way to your machine and simulate the exact same thing, bombarding you with notifications.

STEPS TO REPRODUCE
This is actually hard to reproduce but could possibly be simulated through a bash script.
1. Create an infinite loop
2. Within the loop, insert this code --> zenity --notification --text="test"



OBSERVED RESULT
This should create a notification for each iteration thus simulating the problem

EXPECTED RESULT
Machine hangs/freezes

SOFTWARE/OS VERSIONS
Windows: ?
macOS: ?
Linux/KDE Plasma: Manjaro
(available in About System)
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Although this can be stop through the virtual terminal before user login, it could be annoying to other users
Comment 1 Nate Graham 2021-07-29 19:11:19 UTC
Please attach a backtrace of the crash. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 2 Bug Janitor Service 2021-08-13 04:36:15 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 2021-08-28 04:36:44 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!