New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4.1.6 frequently crashes at Exit with active torrents (Win8.1x64) #10630
Comments
I have the same problem on Windows 10 Home 64-bit qBittorrent version 4.1.6 64-bit |
Try to use this build: Unzip and replace the original 4.1.6 files. |
Unfortunately, those files do not solve the problem. Problem signature: |
Mine keep crashing when starting the app. Have to try multiple times until it can be opened normally. I have to do this every time I wish to open the app. Not sure if it's related but I got plenty of torrents running/seeding. qBittorrent v4.1.6 (64-bit) |
Confirmed. Considering the severity of both this bug, and issue #10581, v4.1.6 should be pulled from the servers. |
Amen. |
Same here, windows 7 x64, qBittorrent 4.1.6 x64. |
done sorry :D |
I'm on Windows 10 LTSC 2019. I just updated to 4.1.6 and it crashes at every single exit. I set torrents to download overnight and set it to Suspend (Sleep) my system once it's done and when I wake up my PC I always get the prompt from Windows that it crashed and to close the program. Never experienced this issue on any previous version. |
If you have any issues with the latest version, please open a new issue report. Remember to search for duplicates first, there is a chance someone else has already reported your issue. Thank you for your contributions. |
Please provide the following information
qBittorrent version and Operating System
4.1.6 64-bit on Windows 8.1 Pro 64-bit (6.3.9600 Build 9600)
What is the problem
"qbittorrent.exe has stopped working."
What is the expected behavior
Normal exit.
Steps to reproduce
Start qBittorrent
Exit qBittorrent
Extra info(if any)
See attached screenshot and Report.wer (in ZIP):
Report.zip
The text was updated successfully, but these errors were encountered: