Speed graph stresses CPU too much/very high CPU usage when showing speed graph #4111

New issue

Closed

opened 2026-02-21 17:08:25 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-21 17:08:25 -05:00

Owner

Originally created by @birdie-github on GitHub (Mar 30, 2016).

When I open Speed graph and set it to 6 hours, qBittorrent 3.3.4 start consuming roughly 75% of CPU (varies from 50% to 80%). The UI becomes extremely laggy and unpleasant to use. When I close this graph, qBittorrent returns to its normals state (0-1% CPU usage).

A newly started qBittorrent does not exhibit this behaviour. It's only after you've been seeding/downloading for at least 4 hours that you see this problem - perhaps you do some very difficult computations or make a lot of invisible paint calls - I've no idea.

PC configuration:

CPU: Intel Core i5 2500@4.1GHz
OS: CentOS 6.7
Linux 4.5 x86_64 vanilla
Qt 4.8.7
Libtorrent: 1.0.8.0
Boost: 1.41.0
NVIDIA blob: 361.28
X.org server: 1.15

Edit: in fact seeding for half an hour and setting graph to 30 minutes is enough to see this problem.

Originally created by @birdie-github on GitHub (Mar 30, 2016). When I open Speed graph and set it to 6 hours, qBittorrent 3.3.4 start consuming roughly 75% of CPU (varies from 50% to 80%). The UI becomes extremely laggy and unpleasant to use. When I close this graph, qBittorrent returns to its normals state (0-1% CPU usage). A newly started qBittorrent does not exhibit this behaviour. It's only after you've been seeding/downloading for at least 4 hours that you see this problem - perhaps you do some very difficult computations or make a lot of invisible paint calls - I've no idea. PC configuration: CPU: Intel Core i5 2500@4.1GHz OS: CentOS 6.7 Linux 4.5 x86_64 vanilla Qt 4.8.7 Libtorrent: 1.0.8.0 Boost: 1.41.0 NVIDIA blob: 361.28 X.org server: 1.15 Edit: in fact seeding for half an hour and setting graph to 30 minutes is enough to see this problem.

deekerman closed this issue

2026-02-21 17:08:27 -05:00

deekerman commented

2026-02-21 17:08:29 -05:00

Author

Owner

@birdie-github commented on GitHub (Mar 30, 2016):

Here's a 3 seconds long strace.log
strace.zip

@birdie-github commented on GitHub (Mar 30, 2016): Here's a 3 seconds long strace.log [strace.zip](https://github.com/qbittorrent/qBittorrent/files/195692/strace.zip)

deekerman commented

2026-02-21 17:08:29 -05:00

Author

Owner

@Chocobo1 commented on GitHub (Mar 30, 2016):

Probably solved in PR #4261.

@Chocobo1 commented on GitHub (Mar 30, 2016): Probably solved in PR #4261.

deekerman commented

2026-02-21 17:08:29 -05:00

Author

Owner

@birdie-github commented on GitHub (Mar 30, 2016):

I hope so. I'm too lazy to check it now - I don't even know if it applies cleanly to the 3.3.x tree.

@birdie-github commented on GitHub (Mar 30, 2016): I hope so. I'm too lazy to check it now - I don't even know if it applies cleanly to the 3.3.x tree.

deekerman commented

2026-02-21 17:08:29 -05:00

Author

Owner

@onto commented on GitHub (Apr 4, 2016):

You can try to build from https://github.com/onto/qBittorrent/commits/v3_3_x

@onto commented on GitHub (Apr 4, 2016): You can try to build from https://github.com/onto/qBittorrent/commits/v3_3_x

deekerman commented

2026-02-21 17:08:29 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Apr 4, 2016):

Already reported and probably fixed by that PR. I am marking that PR for v3.3.5 and I'll review as soon as I can.

@sledgehammer999 commented on GitHub (Apr 4, 2016): Already reported and probably fixed by that PR. I am marking that PR for v3.3.5 and I'll review as soon as I can.