Repository navigation
Open
Description
Bloodborne for Mac 0.5.14: crash report
- Mac: Mac17,5 (Apple A18 Pro), 8 GB, macOS 27.0.1 (Build 26A434)
- Settings: output 1920x1080, upscaler off, cap 60 FPS, fixed timing, full screen
- Session: started 2026-11-09 10:21:10 +05:30, ran 0 min 2 s
- Exit status: 70
- Cause: a check in the renderer failed (the GPU log above says which) (at 10:21:12.464)
- Log: game-2026-11-09_10-21-10.log, 29 lines: 3 critical, 2 errors
Warnings and errors before the cause (1 most recent)
10:21:12.464 CRIT GPU [Debug] <Critical> buffer_cache.cpp:149 BufferCache: Assertion Failed!
game-2026-11-09_10-21-10.log (29 lines around the cause)
10:21:10.574 NOTICE launcher: Bloodborne for Mac 0.5.14 on Mac17,5 (Apple A18 Pro), 8 GB, macOS 27.0.1 (Build 26A434); output 1920x1080, upscaler off, cap 60 FPS, fixed timing, full screen; game folder ~/Downloads/Bloodborne/CUSA03173
10:21:10.711 INFO OK: Bloodborne CUSA03173 with update 1.09
10:21:10.779 INFO Mods: Mac Settings: 26 files
10:21:10.855 INFO Mods: 26 game files replaced, 0 added
10:21:11.244 INFO Bloodborne™ | entry=0xa0 | image=91,042,036 bytes
10:21:11.244 INFO 686 imported symbols; 235,000 relocations; 42 required modules
10:21:11.244 INFO Unavailable non-loadable metadata headers: [9]; not a byte-exact ELF reconstruction
10:21:11.244 INFO Output: ~/Library/Application Support/Bloodborne/out
10:21:11.244 INFO libc _init_env verified RET: True
10:21:11.592 INFO Linked native libc: base=0x56e0000, 202 fallback exports, TLS=1184 bytes; eboot TLS=1872 bytes, fs->gs patched=17127
10:21:11.952 INFO Linked modules: libc.prx@0x56e0000, libSceFios2.prx@0x57c0000; 238 native bindings, 524 imports left to the host runtime, fs->gs patched=17127
10:21:11.983 INFO AppContent profile: SKU=full (probe setting), user params=[13, 0, 0, 0], mounted add-
10:21:12.072 INFO Patches: FPS preset 60; 191 writes from ['60 FPS++']
10:21:12.110 INFO GPU process: starting /private/var/folders/28/snn39
8000
bhn4275vchh5v2mph340000gn/T/AppTranslocation/8E148354-2C13-40E7-92AE-EC355EABB9D3/d/Bloodborne.app/Contents/MacOS/bbgpu-host-macos27
10:21:12.129 INFO bbgpu-host: pid 23696, native arm64, page 16384 bytes
10:21:12.129 INFO bbgpu-host: handshake done: parent pid 23695, guest entry 0x17c000000 bytes, guest range 0x7000000000-0xfc00000000 reserved
10:21:12.129 INFO bbgpu-host: ready: serving the submit ring
10:21:12.129 INFO GPU process: host pid 23696 ready in 19 ms (native arm64, page 16384 bytes); guest entry 0x17c000000 bytes mirrored at 0x7000000000-0xfc00000000
10:21:12.130 INFO [FAST PATH] Tracing disabled (BB_TRACE=0): direct import dispatch active.
10:21:12.170 INFO Settings: ~/Library/Application Support/Bloodborne/bbport.ini
10:21:12.195 INFO Settings: ~/Library/Application Support/Bloodborne/bbport.ini
10:21:12.291 INFO Window: 2710x1638 pixels, density 2.0
10:21:12.464 CRIT GPU [Debug] <Critical> buffer_cache.cpp:149 BufferCache: Assertion Failed!
10:21:12.464 INFO This Mac's GPU allows buffers of 4.0 GiB; the game needs 5 GiB (a Mac with at least 16 GB of memory)
10:21:12.464 CRIT Crash: a check in the renderer failed (the GPU log above says which)
10:21:12.464 ERROR STOP: GPU library assertion failed (see GPU log above)
10:21:12.508 INFO GPU process: host lost (host process exited with status 23) before rendering
10:21:12.508 CRIT Crash: the GPU process could not start (host process exited with status 23). The lines above say why.
10:21:12.583 ERROR launcher: the game stopped with status 70 after 0 min 2 s
Metadata
Metadata
Assignees
Labels
No labels
Activity
byebyevlad commentedon Nov 9, 2026
Looked into this. Short version: I simulated an 8 GB Mac on my 16 GB one. The game starts and plays with a small fix, but your RAM may not be enough. My Mac isn't really limited, so only a test on yours can tell for sure.
Longer version:
The 5 GiB check runs before the memory layout is chosen, but the
runslayout (the default on Macs with 24 GB or less) never needs one buffer that large. I have a small local fix that lets 8 GB Macs start onruns.Tested on an M3 16 GB with
BB_MAX_BUFFER_GIB=4(an 8 GB Mac's limit), about 15 min of play:Memory is the open question:
bbgpu-hostused 6.2 GB andbb-probe3.0 GB, so an 8 GB Mac will likely swap. Happy to share a test build if you want to try it.byebyevlad commentedon Nov 9, 2026
Actually I'll just drop it now so that you don't have to wait for me since you'll likely want to try
Here's a test build: Bloodborne-macOS-0.5.14-4-gfb0fdf2.zip (release notes)
~/Library/Application Support/Bloodborne/user, and copy thesavedatafolder somewhere.Bloodborne.appinto Applications (replace the old one).xattr -dr com.apple.quarantine /Applications/Bloodborne.appPlease tell me whether it starts, roughly what FPS you get, and whether it stutters or freezes. If it crashes, the launcher's crash report is enough. To go back, download 0.5.14 from the official releases page.
byebyevlad commentedon Nov 9, 2026
@hyperscar24-byte sorry forgot to tag you so that you notice
Wooloomooloo2 commentedon Nov 12, 2026
Thanks @byebyevlad for digging into this and for the test build.
@hyperscar24-byte: 8 GB Macs aren't officially supported (#105). The game and its graphics process together use about 9 GB, so expect heavy swapping even when it starts. But if byebyevlad's test build starts and plays for you, please say so here. If it does, a small pull request with the start-up fix is welcome (@byebyevlad), so 8 GB Macs at least get to the game instead of crashing.
Written with Claude Code.
hyperscar24-byte commentedon Nov 13, 2026
byebyevlad commentedon Nov 14, 2026
Thanks @hyperscar24-byte, this is useful: the test build gets past the start-up crash (the game loaded and started rendering), so that part of the fix works.
The new stop is the GPU watchdog: the first frames didn't finish within 3 seconds and the game quit on purpose so it wouldn't freeze the screen. On 8 GB the graphics memory may simply be swapping, so the GPU is slow rather than stuck. Could you try once more with a longer limit? Quit everything else first, then in Terminal:
(adjust the path if the app is elsewhere). Please tell us whether it reaches the title screen or the menu, roughly how long it takes, and attach the crash report if it still stops.
byebyevlad commentedon Nov 14, 2026
@hyperscar24-byte thanks for checking! as the repo owner said, it might not be technically feasible at all, but we've not reached that point yet. try the command above - it will increase auto-quit from 3s to 30s to see whether the game is slow or frozen in your case