qBittorrent 4.3.3 crashing on launch on Mac OS 11.2

[Mr-Beetroot]

Updated to Mac OS Big Sur 11.2 yesterday, qBittorrent 4.3.3 started crashing on launch (minutes long beachball + application not responding in task manager)

Before the OS update, qBittorrent 4.3.3 was working perfectly on version 11.1

[andmpel]

I'm not able to replicate this issue. Have same OS and client. Try uninstalling & reinstalling?

[zzandland]

Can't reproduce on same OS and client version.

[TheYsconator]

I can reproduce this; opening the app (and possibly just clicking on a random spot within the app) makes the app hang and a beach ball appear. Running qBittorrent 4.3.3 on macOS 11.2. If I don't click somewhere, the app does not crash, though it also does not download any torrent. In the (bottom) status bar, to the right, I now have an orange 'connection status' flame; something I don't remember having before upgrading to 11.2.

Downgrading qBittorrent to the first-to-latest version did not resolve the issue. I have (and always have had) firewall enabled. I'm using Little Snitch, but even when I allow all connections on the two qBittorrents that ask for permissions and the macOS kernel, there's no improvement.

To the best of my knowledge, no configuration has changed, besides upgrading macOS and qBittorrent. Before these changes everything worked, after it did not. I do not know if the 'not downloading' and 'app crashing' are related, though they did reveal themselves at the same time.

Let me know if I can help with logs, or in any other way.

[TheYsconator]

Ah; these are the lines containing 'qbittorrent' from my system.log from today. The SIGKILLs are me 'force quitting' the application, though the first line may hint to an issue (?). I do not know if that message also appeared before I encountered any problems with qBittorrent.

Feb  9 10:02:21 Groot com.apple.xpc.launchd[1] (application.org.qbittorrent.qBittorrent.16886065.16886154[4008]): removing service since it exited with consistent failure - OS_REASON_EXEC | Gatekeeper policy blocked execution
Feb  9 10:02:28 Groot com.apple.xpc.launchd[1]: Coalition Cache Hit: app<application.org.qbittorrent.qBittorrent.16886065.16886154(501)> [2052]
Feb  9 10:02:29 Groot com.apple.xpc.launchd[1] (application.org.qbittorrent.qBittorrent.16886065.16886154[4019]): removing service since it exited with consistent failure - OS_REASON_EXEC | Gatekeeper policy blocked execution
Feb  9 10:02:30 Groot com.apple.xpc.launchd[1]: Coalition Cache Hit: app<application.org.qbittorrent.qBittorrent.16886065.16886154(501)> [2052]
Feb  9 10:03:24 Groot com.apple.xpc.launchd[1] (application.org.qbittorrent.qBittorrent.16886065.16886154[4021]): Service exited due to SIGKILL | sent by Dock[421]
Feb  9 10:05:42 Groot com.apple.xpc.launchd[1]: Coalition Cache Hit: app<application.org.qbittorrent.qBittorrent.16886065.16886154(501)> [2052]
Feb  9 10:06:11 Groot com.apple.xpc.launchd[1] (application.org.qbittorrent.qBittorrent.16886065.16886154[4200]): Service exited due to SIGKILL | sent by Dock[421]
Feb  9 10:07:38 Groot com.apple.xpc.launchd[1]: Coalition Cache Hit: app<application.org.qbittorrent.qBittorrent.16886065.16886154(501)> [2052]
Feb  9 10:16:13 Groot com.apple.xpc.launchd[1] (application.org.qbittorrent.qBittorrent.16886065.16886154[4300]): Service exited due to SIGKILL | sent by loginwindow[146]

[Mr-Beetroot]

Still not fixed

[xavier2k6]

To those experiencing this issue, Are you using Apple Silicon hardware?

[TheYsconator]

I'm using a 16" MacBook Pro from 2019.

[Jendker]

I am also on Intel CPU.

[Mr-Beetroot]

qBittorrent 4.3.2 worked on Mac OS 11.1 on M1 Apple Silicon

[TheYsconator]

I resolved the issue on my computer, by removing (nearly) all qbittorrent-related files from my mac. I used Find Any File, searched for 'qbittorrent' and removed everything, except things related to Brew (in the Homebrew directory), ~/.config/qbittorrent and the .app itself.

In particular I removed the SavedApplicationState, caches and qbittorrent's directories in Preferences and App.Supp.

The app now works as expected again. If you are planning on trying the same steps, please do note that for me the listing of my torrents-in-progess was cleared (though not the already downloaded parts).

[psychedelicious]

I have this same issue on an Intel macbook, on Big Sur v11.1. I have the issue on qBittorrent v4.3.3 and, if I recall correctly, on v4.3.2 as well.

If I remove the .fastresume files from /Users/username/Library/Application Support/qBittorrent/BT_backup, qBittorrent opens but of course none of my torrents are there. I don't need do anything else for app to open.

I started adding .fastresume files individually back to BT_Backup, and found that certain .fastresume files caused qBittorrent to crash either on startup, or shortly after interacting with the app in any way. Sometimes it was immediate, sometimes it took a few seconds, but these files cause it to crash every time.

Here are three sanitized example .fastresume files that crash qBittorrent:

sanitized_fastresume_1.fastresume.txt

sanitized_fastresume_2.fastresume.txt

sanitized_fastresume_3.fastresume.txt

Here are three sanitized example .fastresume files that do not crash qBittorrent:

working_sanitized_fastresume_3.fastresume.txt

working_sanitized_fastresume_2.fastresume.txt

working_sanitized_fastresume_1.fastresume.txt

I don't understand this metadata enough to find a commonality between the files that crash the app, but am happy to do more troubleshooting with some guidance.

edit: I sanitized the files by removing the torrent name and tracker(s) from each file. Additionally the unique identifiers in the file names have been removed. I hope this is still useful.

[psychedelicious]

I've attempted to add a new torrent to qBittorrent, which otherwise works so long as I don't load those apparently problematic .fastresume files, and it crashes when doing so. Doesn't matter if I add via magnet link or .torrent file, crashes either way.

[TheYsconator]

To add to psychedelicious' last comment (and to make things more confusing); I also added new torrents (using .torrent files) and have been using qBittorrent normally throughout yesterday without it failing on me.

@psychedelicious does the app also still crash if you remove (or rename) the same files as I did?

[Mr-Beetroot]

I resolved the issue on my computer, by removing (nearly) all qbittorrent-related files from my mac. I used Find Any File, searched for 'qbittorrent' and removed everything, except things related to Brew (in the Homebrew directory), ~/.config/qbittorrent and the .app itself.

In particular I removed the SavedApplicationState, caches and qbittorrent's directories in Preferences and App.Supp.

The app now works as expected again. If you are planning on trying the same steps, please do note that for me the listing of my torrents-in-progess was cleared (though not the already downloaded parts).

This only helps to reinstall the application and run it without any data. As soon as you add torrents it freezes again

[TheYsconator]

For me is has resolved the issue so far, as I did download additional torrents after doing just that, and it has not crashed again since. (I'll poke here if it does crash again of course.)

[psychedelicious]

To add to psychedelicious' last comment (and to make things more confusing); I also added new torrents (using .torrent files) and have been using qBittorrent normally throughout yesterday without it failing on me.

@psychedelicious does the app also still crash if you remove (or rename) the same files as I did?

@TheYsconator @Mr-Beetroot

Starting with qBittorrent not letting me add new torrents, I renamed the same files @TheYsconator did. Then qBittorrent let me add new torrents. My preferences of course were wiped - it was like a totally fresh install. So that's good.

One-by-one, I renamed those files back to their original names, deleting any new version the app had made, and once they were all back, qBittorrent still let me add new torrents, works fine. So... I am confused by that. Doesn't work, delete everything, it works, un-delete everything, still works.

Still crashes with those problematic .fastresume files, though... At least I can add new torrents now though.

BTW, the Find Any File app is great, thanks for the tip!

[TheYsconator]

Hmm if no new .fastresume files cause any issues, I guess it's safe to assume this issue is caused by a migration of some sorts. In that case, I doubt it's worth investigating further, for now.

I think we should close this issue until newly made .fastresume files start causing issues, or qBittorrent starts hanging for people when no migration/ update of sorts has occurred.)

(And yes; when wanting to find stuff on your mac, that app can be a lifesaver. I'm happy to read that you find it useful. :) )

[xavier2k6]

@glassez Thoughts?

[glassez]

@glassez Thoughts?

I'm sorry, there's nothing. It is almost impossible to understand what is causing the crash without being able to reproduce it and debug it. In addition, there is not even a stacktrace that could shed some light on this problem. Unfortunately, I don't have a Mac available so that I can provide full support for related issues.

[Jendker]

@glassez would that work as the stacktrace? https://www.dropbox.com/sh/yn40wuyyw8v1psi/AABfRByF8l8ys8wUSJkyBUOXa?dl=0

[TypeVII]

Same issue here, on Big Sur 11.2.1, tested on SSD and HDD, hangs upon firing up. Extreme lag, downgraded to 4.3.2 works with minor lag. 4.3.3 totally unbearable

[TheYsconator]

@TypeVII Did you try the quasi-solution mentioned earlier? (The search-and-removal of qBittorrent-related files.)

[glassez]

@glassez would that work as the stacktrace? https://www.dropbox.com/sh/yn40wuyyw8v1psi/AABfRByF8l8ys8wUSJkyBUOXa?dl=0

Sorry, it scares me to look for something useful among 40k lines. I was referring to the stack snapshot near the crash point that qBittorrent usually shows if it manages to do so.

[xavier2k6]

@Jendker Post removed.

[TypeVII]

@TheYsconator did that, not working at all, as long the torrent starts downloading everything freezes, even on nvme ssd. Rolled back to 4.3.2 and the freezing isn't that bad only 10% of it. Haven't had any issue prior to Big Sur upgrade.

[TypeVII]

Tested 4.20 all the way to 4.3.2, less freezes but unable to achieve high speed, mostly under 10mbit/s on a 300mbit/s connection. Reverted back to 4.1.9 as someone mentioned on other forums and everything works perfectly, no freezes, no connection issue.

This is for Big Sur.

[glassez]

Hmm if no new .fastresume files cause any issues, I guess it's safe to assume this issue is caused by a migration of some sorts. In that case, I doubt it's worth investigating further, for now.

👍 So, am I closing this Issue? Of course, it would be interesting to compare both (problematic and non-problematic) .fastresume files belonging to the same torrent.

@TypeVII, if you don't experience an app crash on startup, then you are subject to another problem. You can open the appropriate Issue if you want.

[nelsonfigueroa]

I also ran into this issue on MacOS 11.2, on a MacBook Pro 16" 2019. I run Little Snitch on my machine and I noticed that Little Snitch makes qBittorrent unresponsive exactly as described in this thread. Uninstalling Little Snitch solved my issue (simply turning off the network monitor or allowing all connections had no effect).

It's odd because Little Snitch doesn't slow down any other program, and qBittorrent always works fine except when Little Snitch is installed.

[TypeVII]

I also ran into this issue on MacOS 11.2, on a MacBook Pro 16" 2019. I run Little Snitch on my machine and I noticed that Little Snitch makes qBittorrent unresponsive exactly as described in this thread. Uninstalling Little Snitch solved my issue (simply turning off the network monitor or allowing all connections had no effect).

It's odd because Little Snitch doesn't slow down any other program, and qBittorrent always works fine except when Little Snitch is installed.

I too have Little Snitch on, I had it uninstalled and rebooted and it seems fine. Maybe we should report to Little Snitch developer as well.

[xavier2k6]

What version of little snitch are ye using?

[nelsonfigueroa]

I'm using version 5.1.1

[Jendker]

I don't use Little Snitch and I had this issue, that must be something separate.

[glassez]

I don't use Little Snitch and I had this issue, that must be something separate.

As I noticed above you guys discuss different issues here so you confuse each other and reviewers.

[TypeVII]

I don't use Little Snitch and I had this issue, that must be something separate.

As I noticed above you guys discuss different issues here so you confuse each other and reviewers.

I re-tested with and without Little Snitch for the unresponsiveness and this happens for large Torrents. 30GB and above. As long you have a torrent of that file size be it active or not (Seeding or not seeding), it will result in being unresponsive. As long file size of such is being deleted despite having hundreds of small file size torrents like 5GB -> 10GB, everything works just fine, will others check and confirm?

[nelsonfigueroa]

I re-tested with and without Little Snitch for the unresponsiveness and this happens for large Torrents. 30GB and above. As long you have a torrent of that file size be it active or not (Seeding or not seeding), it will result in being unresponsive. As long file size of such is being deleted despite having hundreds of small file size torrents like 5GB -> 10GB, everything works just fine, will others check and confirm?

This didn't work for me. What did make a difference was lowering the Global maximum number of connections to 2, which isn't ideal. Even then, the application would sometimes freeze for a split second.

[theophanemayaud]

Apple Silicon

Nope. I also have this problem, on an older intel 2018 MBP.

Also, I don't have little snitch. It was working fine some time ago, but now when I start it, it gets frozen... I did a reinstall, but nothing changed.

[theophanemayaud]

I just added 2 torrents, and it started working again ! Did some of you try to do that, and did it fix the problem ? It no longer freezes for me.

[lucasapaioa]

I have the same problem, this hasn't been solved !

[RushHour2k5]

I also have this issue. macOS Big Sur 11.3.1, qBittorrent 4.3.5, and Little Snitch 5.1.2.

[RushHour2k5]

Issue still occurring on qBittorrent 4.1.9 and on 4.3.5 even after upgrading to macOS Big Sur 11.4 last night. Workaround for now, move Little Snitch to trash, wait a few moments and then do Command+Z to move it back to the applications folder. Start qBittorrent and then restart Little Snitch again. You will need to do this each time you have to open qBittorrent until it's fixed.

[FranciscoPombal]

We're not interested in cases where the problem happens due to interference with third-party app, since that is most likely a problem with the 3rd party app itself, not qBittorrent. In the past we've observed problems with badly designed software for Windows ("gaming" overlays, overclocking utilities, etc) causing issues with qBittorrent. There is nothing we can do about that. Still, in such cases, feel free to use the discussions tab or the forum to further troubleshoot the problem, if you must still use such software.

[theophanemayaud]

I have the issue on Big Sur without that Little Snitch thing... It comes and goes, un-freezes when I add new torrents, but gets stuck randomly, when I have about 5 or so... Should I try to gather information somehow ?

[FranciscoPombal]

Should I try to gather information somehow ?

Maybe @Kolcha can lend a hand? I don't use Apple products.

[Kolcha]

Maybe @Kolcha can lend a hand?

so, first of all I'm not experienced macOS developer neither even experienced user... I'm just experienced Linux developer running macOS due to historical reasons, and know almost nothing Apple-specific stuff, especially debug techniques. Also I don't own any recent MacBook and have no plans to buy such. sorry...

I only can assume that these freezes happen due to disk I/O issues that lay somewhere very deep in OS. This is just my opinion based on own experience. I noticed that since Catalina something in FS or disk I/O layer has changed significantly, and disk I/O in Catalina is much slower than in Mojave (that's why I keep it on my personal laptop), at least on old laptops I tried (MBP 2013, 2014, 2016). BigSur very likely also inherited this. I'm not using BigSur, it has unacceptable behavior on any old laptop I tried - laptop even can't shutdown or reboot properly with clean just installed OS... Also a lot of software I use every day experience random stuck or crashes (stuck happens very often), so this is unusable for me.

I can't suggest any way to collect info, I'm almost sure that even the try to debug qBittorrent (debug version) will give nothing... there are two most likely situations that may happen:

• debugger is not not attached at all because process in uninterruptible state due to stuck system call (on Linux ps ax shows D in state column in such case, on macOS it should be U according to the docs)
• debugger shows nothing interesting: a lot of threads on epoll_wait() or similar calls

one thing I only can recommend, that is to build qBittorrent by yourself using tools provided by latest Xcode. macOS is known to be very problematic in backward compatibility and subtle issues caused by different versions of software used for build (at least in case of software written in C/C++, know nothing about Objective-C and Swift). with Xcode 12.5 and corresponding SDK something significantly changed again, at work we even experienced build issues...

[FranciscoPombal]

@theophanemayaud

one thing I only can recommend, that is to build qBittorrent by yourself using tools provided by latest Xcode. macOS is known to be very problematic in backward compatibility and subtle issues caused by different versions of software used for build (at least in case of software written in C/C++, know nothing about Objective-C and Swift). with Xcode 12.5 and corresponding SDK something significantly changed again, at work we even experienced build issues...

You could try the latest CI build from here: https://github.com/qbittorrent/qBittorrent/actions?query=branch%3Amaster. It is built with a slightly different, more up-to-date toolchain.

[gauravarora]

FWIW v4.4.0beta2 appears to be working fine where v4.3.7 was not. Perhaps try upgrading.

[Chupaka]

I confirm that upgrading to 4.4.0beta2 solved startup problem.

Long story: On 4.3.7 I had 10 torrents added. It was running smoothly until I restarted the computer. I was able to start qBittorrent only after cleaning BT_backup folder and adding all the torrents back one by one.

4.4.0beta2 successfully started after simple upgrade, no file removal required.

[RushHour2k5]

I’ve been on 4.4.0beta1 for a while and all has been good!

On Aug 17, 2021, at 1:04 PM, Pavel Skuratovich @.***> wrote:

 I confirm that upgrading to 4.4.0beta2 solved startup problem.

Long story: On 4.3.7 I had 10 torrents added. It was running smoothly until I restarted the computer. I was able to start qBittorrent only after cleaning BT_backup folder and adding all the torrents back one by one.

4.4.0beta2 successfully started after simple upgrade, no file removal required.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[jamesblonde007]

I had this problem with 4.3.8 and I am having it right now with 4.3.9 and I experienced the issue with both Big Sur and Monterey. Even with no new torrents added, QBT will just to refuse to start up, usually for several days. Every time I try to restart, I get the spinning ball of death and the program is completely unresponsive. After some time, it will work again for no apparent reason. I suspect this is related to a specific tracker response - that would explain why removing torrents fixes the issue and why others can't replicated the issue (you would need to be connected to the same problem torrent at the same time).

Unfortunately I can't try 4.4 RC1 yet because it is not white listed by my main private tracker.

[laurent22]

Problem still happens with QBitorrent 4.4.0rc1 and Little Snitch. Unfortunately dragging Little Snitch to the trash then Cmd+Z is not a solution since it requires reinstalling Little Snitch every time. As mentioned above it's probably Little Snitch's fault though.