qbittorrent / qBittorrent

qBittorrent BitTorrent client
https://www.qbittorrent.org
Other
27.7k stars 3.92k forks source link

Old issue is back in latest version (recurring silent crash) #20523

Open mrsilva opened 7 months ago

mrsilva commented 7 months ago

qBittorrent & operating system versions

qBitorrent version: 4.6.3 Windows 10 x64 (running under VMWARE)

What is the problem?

qBittorrent simply crashes silently, every day. This used to happen with the old version with libtorrent 2.0, but when libtorrent 1.2 was reinstated this issue disappeared. Now its back with 4.6.3.

There is no Windows event referring to this crash, there is no Windows pop-up or anything, it simply exits. When I restart qBittorrent it does a fast check on all the torrent files and runs normally until the next crash.

I haven't been experiencing any crashes since v4.4.x with libtorrent 1.2 (I always upgrade to the latest version whenever its available)

Steps to reproduce

N/A

Additional context

No response

Log(s) & preferences file(s)

No response

mrsilva commented 3 months ago

Upgraded to 4.6.5 and it is much more stable now. Silently crashes about once per week

xavier2k6 commented 3 months ago

Silently crashes about once per week

It would be most helpful & highly appreciated if you could try to produce a valid stack trace from instructions/method in https://github.com/qbittorrent/qBittorrent/issues/20869#issuecomment-2168749126 (creating a new ticket for same)

mrsilva commented 3 months ago

Are there privacy concerns for users sharing the stack trace? Regarding torrents, passwords, etc?

xavier2k6 commented 3 months ago

Are there privacy concerns for users sharing the stack trace? Regarding torrents, passwords, etc?

The stack trace contains information for where there is an issue in the code or with one of our dependencies, it doesn't contain passwords etc.

xavier2k6 commented 2 months ago

Silently crashes about once per week

It would be most helpful & highly appreciated if you could try to produce a valid stack trace from instructions/method in #20869 (comment) (creating a new ticket for same)

@mrsilva Ping!