Bug 417020 - http.so in quasi tight loop
Summary: http.so in quasi tight loop
Status: RESOLVED DUPLICATE of bug 392768
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: HTTP (show other bugs)
Version: 5.62.0
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-01 12:24 UTC by Marcos Dione
Modified: 2020-02-03 08:59 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcos Dione 2020-02-01 12:24:14 UTC
SUMMARY

I have two processes using some cpu (around 8% each) that figure as:

USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
mdione      2517  0.0  0.2 101660 18124 ?        Ss   ene28   0:00 kdeinit5: Running...
mdione    707738  0.3  0.3 331424 27068 ?        Sl   09:43   0:30  \_ http.so [kdeinit5] https local:/run/user/1000/klauncherjfwQiJ.1.slave-socket local:/run/user/1000/plasmashellKcznzy.18.slave-socket
mdione    709015  0.3  0.3 331424 27068 ?        Sl   09:43   0:30  \_ http.so [kdeinit5] https local:/run/user/1000/klauncherjfwQiJ.1.slave-socket local:/run/user/1000/plasmashelltObnPw.19.slave-socket

If I attach with strace to one of them, I get:

$ strace -tt -p 709015
strace: Process 709015 attached
12:29:01.267475 ppoll([{fd=4, events=POLLIN}], 1, {tv_sec=0, tv_nsec=51044}, NULL, 8) = 0 (Timeout)
12:29:01.267861 write(3, "\1\0\0\0\0\0\0\0", 8) = 8
12:29:01.267983 ppoll([{fd=4, events=POLLIN}], 1, {tv_sec=0, tv_nsec=1000000}, NULL, 8) = 0 (Timeout)
12:29:01.269195 write(3, "\1\0\0\0\0\0\0\0", 8) = 8
12:29:01.269308 ppoll([{fd=4, events=POLLIN}], 1, {tv_sec=0, tv_nsec=1000000}, NULL, 8) = 0 (Timeout)
12:29:01.270552 write(3, "\1\0\0\0\0\0\0\0", 8) = 8

As you can see the loop is quite tight.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian sid
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.5
Comment 1 Kai Uwe Broulik 2020-02-03 08:59:42 UTC

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