← 输入框|github.com|刷新
Skip to content

OrbStack Helper crashes with SIGSEGV inside vmnet on macOS 27.0.1 #2773

Open

Description

@CuWilliams

Describe the bug

OrbStack 2.2.5, macOS 27.0.1 (26A434), Apple silicon, 8 GB, Rosetta enabled, network_bridge: true.

OrbStack Helper crashed twice on 2026-10-27, at 08:35 and 14:30, with EXC_BAD_ACCESS (KERN_INVALID_ADDRESS). The faulting thread is com.apple.framework.vmnet.interface.* both times, with the same stack:

dispatch_async
vmnet __vmnet_start_interface_block_invoke_3
Netrb ____NETRBClientResponseHandler_block_invoke
Just before the crash, vmgr.log shows scon host bridge failed error="vmnet start timed out". The bad address differs between the two crashes (0x60 and 0x23b2).

Workaround in testing: orb config set network_bridge false. After a restart, the bridge-failure line no longer appears. Crash reports and orb report output attached.

To Reproduce

No response

Expected behavior

No response

Diagnostic report (REQUIRED)

orbstack-helper-crash-0835.txt

orbstack-helper-crash-1430.txt

Screenshots and additional context (optional)

No response

Activity

  1. orbstack-bot commented on Oct 27, 2026

    @orbstack-bot

    Hi! Please upload a diagnostic report from the OrbStack menu > Help > Upload Diagnostics (or run orb report) and then paste the output here. The extra info makes it easier for us to debug issues.

    It should look like:

    System info:
    [...]
    
    Full report: orbstack.dev/[...].zip

    (It's safe to post the link publicly — only the OrbStack team can access it.)

  2. CuWilliams commented on Oct 27, 2026

    @CuWilliams
    Author

    To reproduce: not reliably reproducible. It happened twice on 2026-10-27 (08:35 and 14:30 local, UTC−2:30), both times while OrbStack was starting the bridge network (vmgr.log: "scon host bridge failed: vmnet start timed out"), shortly before the crash.

    Expected: OrbStack starts, or logs the vmnet failure, without the Helper crashing.

    Workaround in testing: orb config set network_bridge false, set at about 14:38 the same day. This diagnostic report was taken after that change. I'll report back if the crash happens again with the bridge off.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    t/bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions