qBittorrent icon indicating copy to clipboard operation
qBittorrent copied to clipboard

Crash when using 32bit qBittorrent in 64bit OS due to disk cache

Open raisin8010 opened this issue 4 years ago • 6 comments

Bug report

Checklist

  • [x] I have read the issue reporting section in the contributing guidelines, so I know how to submit a good bug report with the required information
  • [x] I have verified that the issue is not fixed and is reproducible in the latest version
  • [ ] (optional but recommended) I have verified that the issue is not fixed and is reproducible in the latest CI build
  • [x] I have checked the frequent/common issues list and searched the issue tracker for similar bug reports (including closed ones) to avoid posting a duplicate
  • [x] This report is not a support request or question, both of which are better suited for either the discussions section, forum, or subreddit. The wiki did not contain a suitable solution either
  • [x] I have pasted/attached the settings file and relevant log(s) in the Attachments section at the bottom of the report. Mandatory: the settings file and at least the most recent log. See this wiki page if you're not sure where to find them.

Description

qBittorrent info and operating system(s)

  • qBittorrent version: 4.3.6 32bit
  • Operating system(s) where the issue occurs: Win10 64bit 21H1 10.0.19043

What is the problem

My disk cache setting is -1(auto) and my memory size is 128GB. The 32bit program seems to decide use more memory than it can have. When disk cache usage is up to about 1.3GB(the max that it can have), the program will not write it into disk, and the "write cache overload" will increase, until the download speed becomes 0kb/s, sometimes it will crash directly. 1

Detailed steps to reproduce the problem

  1. Run 32bit qBittorrent in 64bit OS on a large memory computer.
  2. Download a file whose size is larger than 2GB.
  3. When disk cache usage is up to about 1.3GB, it will crash or the speed will become 0kb/s.

What is the expected behavior

Write cache won't overload and the program do not crash.

Attachments

qBittorrent.txt qbittorrent.log

raisin8010 avatar Aug 02 '21 09:08 raisin8010

@woshiniming007 Any crash report/stack trace?, also - is there any reason why you don't use the 64bit version of qBittorrent on your 64bit OS?

xavier2k6 avatar Aug 02 '21 11:08 xavier2k6

@woshiniming007 Any crash report/stack trace?, also - is there any reason why you don't use the 64bit version of qBittorrent on your 64bit OS?

Usually it doesn't crash and the speed becomes zero. Sometimes it just hangs and seems not to generate report. I didn't find a report in profile directory. No, I just report the bug.

raisin8010 avatar Aug 02 '21 14:08 raisin8010

This sounds like a libtorrent issue. @arvidn ping!

ghost avatar Aug 02 '21 15:08 ghost

which version of libtorrent is this?

arvidn avatar Aug 02 '21 17:08 arvidn

which version of libtorrent is this?

Library Version
libtorrent-rasterbar 1.2.14+gitc996ed7ef7

xavier2k6 avatar Aug 02 '21 17:08 xavier2k6

@glassez @Chocobo1 Unsure if this may have been related to #21003

I consider it to be obsolete (4.3.6 32bit) now though since we no longer provide 32bit versions etc & would like to close.

xavier2k6 avatar Sep 30 '24 14:09 xavier2k6

  • This ticket has been closed due to being "out-of-date", and thus either most likely resolved in recent versions or no longer applicable.

  • If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

  • A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression. Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar. Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

  • Thank you for your contribution(s).

xavier2k6 avatar Mar 12 '25 18:03 xavier2k6