mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Qbittorrent 4.0 Windows High Cpu Usage, Process Won't Die After Exiting #6314
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#6314
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CeruleanSky on GitHub (Nov 20, 2017).
Originally assigned to: @glassez on GitHub.
qBittorrent version and Operating System
Qbittorrent 4.0..0 x64 - qbittorrent_4.0.0_x64_setup.exe
What is the problem
Qbittorrent has high cpu usage. It appears to be one thread. After exiting, while most of the windows are destroyed, the thread continues to run forever.
The program does not appear to be frozen.
What is the expected behavior
Qbittorrent to exit after a few seconds or minutes.
Steps to reproduce
Open Qbittorrent. Close Qbittorrent.
Extra info(if any)
Stack Trace of High CPU thread from Process Hacker
Edit: Please use stack traces and windbg output with symbols below
In case this is related. I also suffer from Issue 7751, RSS feeds not updating, only one updatng, or only updating once they are added and never again. The icons also remain in the "updating" state.
@slrslr commented on GitHub (Nov 20, 2017):
Here are similar or related issues:
https://github.com/qbittorrent/qBittorrent/issues/5097
https://github.com/qbittorrent/qBittorrent/issues/1332
@sledgehammer999 commented on GitHub (Nov 20, 2017):
That stacktrace is a bit useless without function names. Does process hacker allow to load "debug symbols" or "PDB database/file"? If yes, load
qbittorrent.pdb(found in program files) and take another stacktrace.@CeruleanSky commented on GitHub (Nov 20, 2017):
@slrslr
To differentiate from those two tickets:
This started on 4.0.0 , in regards to #5097 all previous versions worked fine.
Inregards to #1332 it isn't frozen or at 0% cpu usage, but listed as using ~100% of the cpu the thread is on.
@sledgehammer999
Just had to add the path to the symbols in the options.
Here you go, it does seem it might be RSS and #7751 related.
The problem seems to go away when RSS is disabled.
I hit refresh and while each stack trace was different, it seems that this part is common to them all.
qbittorrent.exe!RSS::Private::Parser::parseAtomChannel+0x2b3Stacktrace 1
Stacktrace 2
Stacktrace 3
Stacktrace 4
@CeruleanSky commented on GitHub (Nov 20, 2017):
I also finished getting windbg installed and working with
|* ~* kpShould be a bit more helpful, here is that 0x2b3 line referenced above:
qbittorrent!RSS::Private::Parser::parseAtomChannel(class QXmlStreamReader * xml = 0x000000a2`d3bfbc08)+0x2b3 [g:\qbittorrent\qbittorrent-4.0.0\src\base\rss\private\rss_parser.cpp @ 438]
Just the thread above:
Everything:
@sledgehammer999 commented on GitHub (Nov 20, 2017):
@glassez this performance issues seem related to RSS. Care to take a look?
(see stracktraces above)
@CeruleanSky thanks, those seem helpful now.
@CeruleanSky commented on GitHub (Nov 20, 2017):
I started experimenting with what feeds cause a failure and tried some external ones I use with other apps.
While not containing torrents, this feed worked with the old parser showing all the articles.
It seems to run indefinitely with the new parser.
Getting this to work again and show the articles like the old parser did would help with feeds where not every one has a torrent, such as those that mix posts and torrents, or other irregular torrent feeds causing issues, like if a search for torrents is no longer returning torrents.
https://www.reddit.com/.rss
https://www.youtube.com/feeds/videos.xml?channel_id=UCzQUP1qoWDoEbmsQxvdjxgQ
@PinaColonic commented on GitHub (Nov 20, 2017):
Do you use an IP filtlist? I was seeing incredibly high CPU and problems starting qbit on Linux until I disabled it with 4.0. Definitely something broken there on Linux...
@glassez commented on GitHub (Nov 21, 2017):
Working on it...
@CeruleanSky commented on GitHub (Nov 21, 2017):
@PinaColonic As far as I can tell I am not having any issues with using a IP filterlist and cpu usage. Might want to get a backtrace of the high cpu thread. After it is launched and attached and you ensure you have debug symbols installed, braakpoint In gdb run
thread apply all bt. Probably best to open another ticket for that issue or see if one exists.@glassez Thank you, let me know if there is anything else I can do to help.
@gndqb commented on GitHub (Nov 21, 2017):
Did some testing with disabling RSS. If I disable RSS (untick fetching and auto-downloading in Options/RSS), and then end task in task manager (because it doesn't end by exit), then after restart QBT has normal cpu usage of cca 1-2% cpu.
Then I go to Options/RSS, and enable RSS (fetching and auto DL). Immediately RSS updates, new torrents are added, and CPU jumps to 50-55%, and RSS freezes. Looking at RSS list, frozen icons are on Demonoid rss, all others have regular icons. CPU is locked on cca 55%.
I hit Update All, and all RSS icons freeze (grey circles not moving). CPU stays on 55%. RSS not updating anymore after that.
connected to this: https://github.com/qbittorrent/qBittorrent/issues/7751
@glassez commented on GitHub (Nov 21, 2017):
Please provide affected feed URL.
@MithranArkanere commented on GitHub (Nov 21, 2017):
As far as I can tell, the problem only happens with Atom feeds.
After using a tool such as this one:
http://feedmix.novaclic.com/atom2rss.php
To convert the feed, the problem no longer happened.
@glassez commented on GitHub (Nov 21, 2017):
The problem is already located, the fix coming soon.
This has another kind of issue. Can someone confirm this feed works correctly in v3.3.x?
@CeruleanSky commented on GitHub (Nov 21, 2017):
Tried the youtube and reddit feeds in qbittorrent 3.3.16
@CeruleanSky commented on GitHub (Nov 30, 2017):
Can confirm that qBittorrent 4.0.2 win x64 fixes all the issues with the cpu usage I had.
All rss feeds work, at least of mine, loading properly.
qBittorrent terminates after closing the window within a very short time.
Thank you.
@ghost commented on GitHub (Nov 30, 2017):
I'm still having the issue described in #7873 - any advice?