Bug 400155 - KIO http.so periodically loads CPU
Summary: KIO http.so periodically loads CPU
Status: RESOLVED DUPLICATE of bug 392768
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: HTTP (show other bugs)
Version: 5.50.0
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-22 12:30 UTC by Lastique
Modified: 2020-01-02 13:31 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
High CPU load by http.so 1 (100.45 KB, image/png)
2018-10-22 12:30 UTC, Lastique
Details
High CPU load by http.so 2 (68.98 KB, image/png)
2018-10-22 12:30 UTC, Lastique
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lastique 2018-10-22 12:30:10 UTC
Created attachment 115826 [details]
High CPU load by http.so 1

Periodically, http.so processes started by Ktorrent begin to load CPU intensively. There are multiple such processes running, so the total effect is 20-40% CPU load, according to KSysGuard. This period of high CPU usage lasts for about 20-30 seconds, then the CPU load goes back to normal. These high CPU usage periods happen repeatedly at various intervals, I've seen anywhere from about a minute and around 5 minutes. I suspect, the intervals may have to do with how often Ktorrent contacts the torrent trackers.

I've attached a couple screenshots showing high CPU usage.


SOFTWARE VERSIONS

Kubuntu 18.10 x86_64
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50
Qt Version: 5.11.1
Comment 1 Lastique 2018-10-22 12:30:33 UTC
Created attachment 115827 [details]
High CPU load by http.so 2
Comment 2 Kai Uwe Broulik 2018-10-26 08:59:11 UTC
I have occasionally observed that behavior. From what I can tell for me it happened when a QML Image was downloading a remove image. This would use KIO AccessManagerFactory and translate QNetworkAccessManager calls to KIO and somewhere in there it ends up hogging CPU.
Comment 3 Kevin Funk 2020-01-02 13:31:02 UTC
Bug 392768 seems to be origin of this issue, too.

*** This bug has been marked as a duplicate of bug 392768 ***