Search existing issues
Describe the bug
Description
OpenScreen crashed immediately after stopping a recording on macOS. The recording artifacts were still written successfully: MP4, cursor metadata, and session JSON were present and readable afterward.
This looks like a shutdown/finalization crash rather than a corrupted recording write.
Environment
- OpenScreen version: 1.5.0
- macOS: 26.4.1
- CPU: Apple Silicon / ARM64
- Capture path: native macOS capture pipeline / ScreenCaptureKit
- Cursor capture mode: editable overlay
What happened
- Recorded a screen session.
- Stopped the recording.
- The app crashed shortly after stopping.
- The video was recoverable and valid.
- Cursor metadata was also recoverable.
Crash evidence
macOS crash report summary:
- Exception:
EXC_BREAKPOINT
- Signal:
SIGTRAP
- Faulting thread:
CrBrowserMain
- Stack involved Electron / Node / V8 async filesystem cleanup.
- Relevant frame included
node::fs::FileHandle::CloseReq::Resolve.
Unified log around the stop event showed ScreenCaptureKit teardown messages, including repeated:
_SCStream_RemoteAudioQueueOperationHandlerWithError: streamOutput NOT found. Dropping frame
### Expected behavior
After finishing recording I'd expect it to save and open the editor.
### To Reproduce
_No response_
### Screenshots
_No response_
### OS
None
### OS Version
_No response_
### Other OS
_No response_
### Browser
None
### Browser Version
_No response_
### Other Browser
_No response_
### Device Type
None
### Other Device
_No response_
### Additional context
_No response_
Search existing issues
Describe the bug
Description
OpenScreen crashed immediately after stopping a recording on macOS. The recording artifacts were still written successfully: MP4, cursor metadata, and session JSON were present and readable afterward.
This looks like a shutdown/finalization crash rather than a corrupted recording write.
Environment
What happened
Crash evidence
macOS crash report summary:
EXC_BREAKPOINTSIGTRAPCrBrowserMainnode::fs::FileHandle::CloseReq::Resolve.Unified log around the stop event showed ScreenCaptureKit teardown messages, including repeated: