mirror of
https://github.com/PlayCover/PlayCover.git
synced 2026-04-26 16:25:54 +03:00
[GH-ISSUE #1981] [Bug]: Game crash on M1 Mac due to multi-threaded fork (SIGABRT) #1310
Labels
No labels
UI
app-support
bug
bug
documentation
duplicate
enhancement
game-support
good first issue
help wanted / caution
inactive
invalid
macos-beta
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/PlayCover#1310
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @veskoap on GitHub (Sep 25, 2025).
Original GitHub issue: https://github.com/PlayCover/PlayCover/issues/1981
Describe the bug
When launching Destiny:Rising, a "Problem Report for Game" window appears shortly after launch, indicating a crash has occurred. However, the main game process is unaffected and continues to run and function correctly.
The crash log shows an
EXC_CRASH (SIGABRT)signal, with the termination reason beingAbort trap: 6. The key application-specific information points to the root cause:multi-threaded process forkedandcrashed on child side of fork pre-exec.This indicates that a child process is intentionally aborting itself because it was created via an unsafe
fork()system call from a multi-threaded parent process, a known instability on macOS.Steps to reproduce
Expected behaviour
The game should launch and run without generating any crash reports for its child processes. The
fork()system call should ideally be prevented by the sandbox to ensure stability.Crash log
What version of PlayCover are you using?
3.1.0
What version of macOS are you using?
Sonoma (macOS 14)
Issue Language
@veskoap commented on GitHub (Sep 25, 2025):
Hi everyone,
I've looked into the root cause of this issue and see that crash is related to an unsafe fork() call that can be prevented with a sandbox rule.
I'm currently working on a patch and plan to submit a pull request for it shortly. I'll link it to this issue when it's ready for review.