qbittorrent 4.1.6 not working crashes on startup on Windows XP x64
Posted: Fri May 10, 2019 7:00 pm
I have upgraded qbittorrent 4.1.5 to qbittorrent 4.1.6 a few days ago. I have noticed that most of the times I open it it just crashes. It shows me the "Application not responing" window and makes me choose between closing it and online help.
Some other times instead it opens and appears to be working fine, but this happens without an apparent reason and very rarely. Once I close it it is back to startup crash.
I have tried:
Closing it and opening it again;
Shutting down and rebooting the computer;
Reinstalling the application;
Terminating the antivirus processes and reinstalling the app;
Opening qbittorrent with admin privileges.
But none of this has had any result.
I am running on Windows XP x64. My computer is very old, but I have noticed other people here have the same problem with the new version as well.
I would be grateful if you could provide me with any help.
Thank you.
EDIT #1: I have managed to open qbittorrent and keeping it opened for several hours without ever closing it. I have downloaded a 900+MB torrent, which I verified to be integer (it is a video). Upload and download thus seem to be workig fine (I have also uploaded 600+MB of data in this session), which makes me guess there is no problem of compatibility with my OS nor of internal functioning of the app. It should be just a problem with the initialization of qbittorrent.
EDIT #2: After over 1GB of upload I closed qbittorrent, and as expected I wasn't able to open it again for a few times. I got the usual message "qbittorrent.exe stopped working". On the fifth/sixth attempt it successfully opened and started uploading without crashing. After this I closed it and got back to the same problem of not being able of predicting when it will work.
I also tried changing in C:\Users\<username>\AppData\Roaming\qBittorrent\qBittorrent.ini the string "DownloadTrackerFavicon=true" into "DownloadTrackerFavicon=false" but the problem didn't change.
I am reporting this although I know there are more skilled people working on this issue on https://github.com/qbittorrent/qBittorrent/issues/10581 and it seems the problem might be in something related to MySQL.
Some other times instead it opens and appears to be working fine, but this happens without an apparent reason and very rarely. Once I close it it is back to startup crash.
I have tried:
Closing it and opening it again;
Shutting down and rebooting the computer;
Reinstalling the application;
Terminating the antivirus processes and reinstalling the app;
Opening qbittorrent with admin privileges.
But none of this has had any result.
I am running on Windows XP x64. My computer is very old, but I have noticed other people here have the same problem with the new version as well.
I would be grateful if you could provide me with any help.
Thank you.
EDIT #1: I have managed to open qbittorrent and keeping it opened for several hours without ever closing it. I have downloaded a 900+MB torrent, which I verified to be integer (it is a video). Upload and download thus seem to be workig fine (I have also uploaded 600+MB of data in this session), which makes me guess there is no problem of compatibility with my OS nor of internal functioning of the app. It should be just a problem with the initialization of qbittorrent.
EDIT #2: After over 1GB of upload I closed qbittorrent, and as expected I wasn't able to open it again for a few times. I got the usual message "qbittorrent.exe stopped working". On the fifth/sixth attempt it successfully opened and started uploading without crashing. After this I closed it and got back to the same problem of not being able of predicting when it will work.
I also tried changing in C:\Users\<username>\AppData\Roaming\qBittorrent\qBittorrent.ini the string "DownloadTrackerFavicon=true" into "DownloadTrackerFavicon=false" but the problem didn't change.
I am reporting this although I know there are more skilled people working on this issue on https://github.com/qbittorrent/qBittorrent/issues/10581 and it seems the problem might be in something related to MySQL.