Bug 408771

Summary: CPU @100% while downloading large files with Chrome
Product: [Plasma] plasmashell Reporter: Massimo Callegari <massimocallegari>
Component: Task Manager and Icons-Only Task Manager widgetsAssignee: Eike Hein <hein>
Status: RESOLVED WORKSFORME    
Severity: normal CC: jkillius, kde, kde, kdelibs-bugs-null, lemmyg, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.16.0   
Target Milestone: 1.0   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: plasmasheel log
dbus-monitor log

Description Massimo Callegari 2019-06-16 10:21:36 UTC
I'm a bit surprised nobody reported this yet.
It bothers me since months, but I can't really tell exactly from which Frameworks version.

STEPS TO REPRODUCE
1. Open Google Chrome (my version is 75.0.3770.90, but any version will do)
2. go to a page where you can download a large file (e.g. https://download.qt.io/official_releases/qt/5.12/5.12.3/)
3. download a >1GB file
4. Enjoy your CPU going at 100% just to show a green bar progressing
5. (bonus) Enjoy your laptop ventilation going crazy for the whole download duration

OBSERVED RESULT
CPU cores going @100%

EXPECTED RESULT
A network download must not bother a CPU at all.
There is clearly a bug in the notification system (in particular the progress bar system) where someone forgot to add a sleep call when polling the download progress.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon
KDE Plasma Version: 5.16
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.3
Comment 1 Massimo Callegari 2019-06-16 10:27:34 UTC
For the record, the process eating up all the CPU is plasmashell.
Comment 2 Kai Uwe Broulik 2019-06-17 07:29:48 UTC
Are you using plasma-browser-integration?
Comment 3 David Edmundson 2019-06-17 11:01:14 UTC
Please provide output of 

QSG_INFO=1 plasmashell --replace

(just the first 20 lines or so)

During download can you run "dbus-monitor" and capture the sample of a few seconds
Comment 4 David Edmundson 2019-06-17 21:34:15 UTC
marking as needsinfo
Comment 5 Massimo Callegari 2019-06-18 17:26:12 UTC
Created attachment 120980 [details]
plasmasheel log
Comment 6 Massimo Callegari 2019-06-18 17:26:39 UTC
Created attachment 120981 [details]
dbus-monitor log
Comment 7 Massimo Callegari 2019-06-18 17:27:15 UTC
> Are you using plasma-browser-integration?

Yes, 5.16.0

Requested logs attached.
Comment 8 David Edmundson 2019-06-18 18:00:36 UTC
Didn't reveal much.

Animation driver was synced correctly. DBus rate was once per second which is sane. 



Next steps:
 - if you remove klipper does that fix anything?
 - if you remove the notification widget does that fix anything?
Comment 9 David Edmundson 2019-06-18 18:02:16 UTC
Edit, ignore the comment about klipper. If it is the bug I'm thinking of then changing klipper won't fix anything.
Comment 10 Massimo Callegari 2019-06-18 18:21:00 UTC
Which one is the notification widget and how do I remove it?
Comment 11 Christoph Feck 2019-07-03 17:01:59 UTC
Right-click the system tray expander arrow > Configure System Tray > General Tab > Extra Items > Notifications checkbox
Comment 12 Massimo Callegari 2019-07-03 20:44:32 UTC
Without notifications, CPU usage is definitely at normal levels
Comment 13 Jan Killius 2019-09-01 15:35:02 UTC
I get the same problem. I can resolve the notification stuff but the Networkmanager applet is creating high cpu when connecting.
Comment 14 galder 2022-01-30 15:53:54 UTC
Looks like an old issue. Setting it to needs more info.
Please try with a newer version(plasma 5.23.5) and if this is not an issue any more let us know.
Bugs placed into NEEDSINFO status will receive a reminder if the ticket:

    Is at least 15 days old
    Has not received any comment within 15 days

If a bug remains in NEEDSINFO for another 15 days with no comment, it will be closed as RESOLVED > WORKSFORME.
If a bug remains in NEEDSINFO with a comment provided within less than 15 days, no action will be taken (as it does not meet the above criteria).
Comment 15 Bug Janitor Service 2022-02-14 04:36:31 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 16 Bug Janitor Service 2022-03-01 04:36:43 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!