mirror of
https://github.com/shadps4-emu/shadPS4.git
synced 2026-04-25 15:56:00 +03:00
[GH-ISSUE #2887] [GAME BUG]: Crashes on Bloodborne [CUSA03023] with shadPS4 0.8.0 #925
Labels
No labels
Bloodborne
bug
contributor wanted
documentation
enhancement
frontend
good first issue
help wanted
linux
pull-request
question
release
verification progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shadPS4#925
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 @ylorn on GitHub (May 7, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/2887
Checklist (we expect you to perform these steps before opening the issue)
Describe the Bug
After launching the game, it runs for several seconds, and then crashes.
Here is the crash reports from the macOS system.
Full crash report can be found in shadps4-2025-05-07-142045.zip
Reproduction Steps
Specify OS Version
macOS Sequoia 15.4.1 (24E263)
CPU
Apple M3 Ultra
GPU
Apple M3 Ultra
Amount of RAM in GB
512 GB
Amount of VRAM in GB
464 GB
Log File
shad_log.txt
@naterfute commented on GitHub (May 10, 2025):
+1 Tried this on 8.0.0 and got an instant crash. When using the lastest pre-release I got the
"Unabel to reserve Virtual address space: Not enough Memory resources are available to process this command."
@ihavenoface5 commented on GitHub (May 10, 2025):
There is a workaround that worked for me found in https://github.com/shadps4-emu/shadPS4/issues/2897
Create a shortcut to Bloodborne (right click, create shortcut). Launch from the shortcut.
@StevenMiller123 commented on GitHub (May 11, 2025):
@ItsBildo @naterfute @ihavenoface5
The issues you three are describing are unrelated to the original issue. macOS works completely differently from Windows, and never hits the assert you are describing.
@Navixer commented on GitHub (Jun 6, 2025):
I have the same problem. It crashes after wandering a little bit around in the swamps area. When I start a new game it also crashes when the cutscene is over. This didn't use to happen. I used to play it without any crashes around the version 0.5.0. I played it for 20 hours. I have a Mac mini M4.
Edit: I have tried it and it doesn't load swamps anymore. It just immediately crashes when I try to load into a game.
@ylorn commented on GitHub (Jun 6, 2025):
Yeah, mine crashes right after the cutscene also.
@Navixer commented on GitHub (Jun 10, 2025):
shad_log.txt
Using the Apple's console it shows the crashed thread. It is the thread 16. And I added Shadps4 debug file
General Info:
Process: shadps4 [10973]
Path: /Applications/shadps4.app/Contents/MacOS/shadps4
Identifier: com.shadps4-emu.shadps4
Version: 0.9.1 WIP (1.0.0)
Code Type: X86-64 (Translated)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2025-06-10 20:53:30.8625 +0300
OS Version: macOS 15.5 (24F74)
Report Version: 12
Anonymous UUID: B2F44D6E-F2E6-B055-6FF9-AD285D457653
Sleep/Wake UUID: 9EB208CB-C662-4F22-A2EC-A3CD04BEE5CC
Time Awake Since Boot: 640000 seconds
Time Since Wake: 403321 seconds
System Integrity Protection: enabled
Notes:
RIP register does not match crashing frame (0x2000075DD7F vs 0x7004ED7ABC)
Crashed Thread: 16 shadPS4:GpuCommandProcessor
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5
Terminating Process: exc handler [10973]
Error Formulating Crash Report:
RIP register does not match crashing frame (0x2000075DD7F vs 0x7004ED7ABC)
Thread 16 Crashed:: shadPS4:GpuCommandProcessor
0 0x7004ed7abc ???
1 shadps4 0x20000f413e1 0x20000000000 + 15995873
2 shadps4 0x20000f3ef6b Vulkan::Presenter::PrepareFrameInternal(Common::SlotId, Libraries::VideoOut::PixelFormat, bool) + 795
3 shadps4 0x20000ba6200 0x20000000000 + 12214784
4 shadps4 0x20000ba534f Libraries::VideoOut::VideoOutDriver::SubmitFlip(Libraries::VideoOut::VideoOutPort*, int, long long, bool) + 351
5 shadps4 0x20000bad5a8 0x20000000000 + 12244392
6 shadps4 0x20000ed69bd 0x20000000000 + 15559101
7 shadps4 0x20000edb652 0x20000000000 + 15578706
8 shadps4 0x20000ed646c 0x20000000000 + 15557740
9 shadps4 0x20000ed8557 0x20000000000 + 15566167
10 libsystem_pthread.dylib 0x7ff80e872df1 _pthread_start + 99
11 libsystem_pthread.dylib 0x7ff80e86e857 thread_start + 15
@StevenMiller123 commented on GitHub (Jun 29, 2025):
@ylorn The issue reported by Navixer is different from the one you opened this issue with.
Is the original problem "After launching the game, it runs for several seconds, and then crashes" still present?
@ylorn commented on GitHub (Jul 9, 2025):
@StevenMiller123 Tried with 0.9.0 the same crash happens after creating the character. The crash occurs after the cutscene starts and before it ends.
Attaching the crash reports and shadPS4 logs.
shad_log.txt
shadps4-2025-07-01-150007.ips.zip
@Missake212 commented on GitHub (Jul 10, 2025):
Sorry to ask you this but could you test 0.10.0? 0.9.0 is nearly a month and a half old at this point so perhaps the new release fixed it.
@ylorn commented on GitHub (Jul 14, 2025):
Sure. Just tried with 0.10.0. Good news, the original crash is no longer seen. But a new crash happened when encountering the first enemy.
shadps4-2025-07-13-212924.ips.zip
shad_log.txt
@Missake212 commented on GitHub (Jul 19, 2025):
Late response but you should probably try it again without the patches, also if the original crash doesn't happen anymore this issue can probably be closed.
@Reita111 commented on GitHub (Jul 19, 2025):
Help me solve the problem I tried to run order 1886 and after the logo and Sony Monica the game crashes with this error
Debug] liverpool.h:114 SearchBinaryInfo: Unreachable code!
Shader binary info not found
@Missake212 commented on GitHub (Jul 19, 2025):
@Reita111 this issue has nothing to do with Death Stranding, but I'm pretty sure this is the expected behavior of the game currently so only thing you can do is wait for fixes.
@Reita111 commented on GitHub (Jul 19, 2025):
I understand, well, I just wanted to ask how to fix the error, I didn't want to create another topic
@Reita111 commented on GitHub (Jul 19, 2025):
I mean The Order 1886
@Missake212 commented on GitHub (Jul 19, 2025):
@Reita111 I meant The Order too sorry, but like I was saying it's best to open a new issue since this one has nothing to do with The Order (but in your case like I said I'm pretty sure that's just the current behavior and not a bug).
@StevenMiller123 commented on GitHub (Aug 27, 2025):
Since the original issue is reportedly fixed, I'm closing this issue.
@ylorn please open a separate issue for this new crash you're encountering. Also make sure to test with all patches disabled, an unmodified game dump, and preferably with the latest pre-release build.