obsproject / obsproject/obs-studio

Crash (EXC_BAD_ACCESS in Qt event dispatch) after ScreenCaptureKit stream disconnect (-3805) during long-running session on macOS 26

Open
#13,755 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
76.4k
Forks
10.2k
Avg merge
4d 23h
Merged PRs (30d)
12

Description

Operating System Info

macOS 26

Other OS

macOS 26.5.2 (25F84, Tahoe)

OBS Studio Version

32.2.1

OBS Studio Version (Other)

No response

OBS Studio Log URL

(Relevant log excerpt included below; session log available on request)

OBS Studio Crash Log URL

https://obsproject.com/logs/crashes/qn25A838mJxH7zXI

Expected Behavior

OBS keeps running (or handles the capture-stream disconnect gracefully) when the Mac sleeps and wakes while OBS is left open with a macOS Screen Capture source.

Current Behavior

OBS intermittently crashes with EXC_BAD_ACCESS (SIGSEGV)KERN_INVALID_ADDRESS at 0xef00000002000030 (possible pointer authentication failure) — on the main thread inside Qt event dispatch (QCoreApplicationPrivate::sendPostedEventsQObject::event → OBS callback → QtWidgets). This looks like a use-after-free of a QObject.

Timeline from the session log:

  1. OBS launched 2026-07-30 15:00 JST, used for a recording (which finished cleanly), then left running.
  2. 18:49 — last log line of the session:
    [ mac-screencapture ]: Stream stopped with error -3805 ("The stream stopped because the application connection was interrupted")
    
    The Mac went to sleep with a macOS Screen Capture source active.
  3. Nothing further was logged. The next morning (2026-07-31 10:13 JST, ~19h after launch) OBS crashed with the attached report. The next session's log starts with Crash or unclean shutdown detected.

The same -3805 ScreenCaptureKit disconnect appears in other session logs as well; the crash appears to require the sleep/disconnect + long-running session combination, so it is intermittent.

Steps to Reproduce
  1. Add a macOS Screen Capture source
  2. Leave OBS running and let the Mac go to sleep (e.g. overnight)
  3. Wake the Mac and interact with OBS
  4. Intermittently crashes with the attached crash report
Anything else we should know?
  • No third-party plugins installed (no ~/Library/Application Support/obs-studio/plugins directory exists)
  • Faulting thread 0 top frames: QtCore +0xf32f0OBS +0x2c8c48QtCore +0xf3804QtWidgets +0x12ce24QtWidgets +0x1288a8QtWidgets +0x135d98QtCore +0xf3804QObject::event +672QApplicationPrivate::notify_helper +332
  • Hardware: MacBook Pro (MacBookPro18,3, M1 Max), Apple Silicon build
  • Possibly related (capture freeze after sleep, but no crash): #8928, #11435

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked crash report and the macOS Screen Capture source handling around the logged -3805 stream disconnect. Trace the path from the disconnect through Qt event dispatch and reproduce with a Screen Capture source across sleep and wake. Done means OBS remains stable and handles the interrupted stream without the reported crash.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, macos
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.