You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've only recently started using orbstack but it's consistently crashed on two different computers under two different (but both heavy IO workloads).
First is on version Version: 2.1.1 (2010100) Commit: 5938f7b0d94c0f51823fa763326a74302524c332 (v2.1.1) on a M4 16GB Mac Mini. The crashes would happen while downloading large files using SABNzbd
Second on version Version: 2.1.3 (2010300) Commit: 7a3258b7336a8a47b75771e87ef7b74ba4bba8eb (v2.1.3) on a 48GB M4 Pro running a data ingestion job on Clickhouse.
This looks to be the same or a very similar issue to #2088. When this happens, docker ps and docker stats hang without returning anything. The internal stats in the orbstack UI also doesn't load. And on the M4 Pro Macbook I saw a dialog about a network disconnect
Report uploads:
OrbStack info:
Version: 2.1.3
Commit: 7a3258b7336a8a47b75771e87ef7b74ba4bba8eb (v2.1.3)
System info:
macOS: 15.5 (24F74)
CPU: arm64, 14 cores
CPU model: Apple M4 Pro
Model: Mac16,7
Memory: 48 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2026-05-19T18-38-57.973115Z.zip
and
OrbStack info:
Version: 2.1.1
Commit: 5938f7b0d94c0f51823fa763326a74302524c332 (v2.1.1)
System info:
macOS: 26.3 (25D125)
CPU: arm64, 10 cores
CPU model: Apple M4
Model: Mac16,10
Memory: 16 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2026-05-19T18-42-01.932903Z.zip
@kdrag0n can you elaborate at all on the cause or fix? Trying to understand if this is a kind of fluke that's unlikely to occur again or if this is something that's prone to happen given the complexity of the disk operations and the solution here just patches one more specific cause
Hard to say. It's a very rare deadlock but some users were running into it quite consistently with certain workloads. None of us have ever been able to reproduce it.
Activity
kdrag0n commentedon May 21, 2026
Fixed for the next version.
mwalkerr commentedon May 24, 2026
@kdrag0n can you elaborate at all on the cause or fix? Trying to understand if this is a kind of fluke that's unlikely to occur again or if this is something that's prone to happen given the complexity of the disk operations and the solution here just patches one more specific cause
kdrag0n commentedon May 24, 2026
Hard to say. It's a very rare deadlock but some users were running into it quite consistently with certain workloads. None of us have ever been able to reproduce it.
kdrag0n commentedon Jun 4, 2026
Released in v2.2.0.