8000 Crash while using Randomizer Mod · Issue #92 · Wooloomooloo2/bloodborne_mac_port · GitHub
[go: up one dir, main page]

Skip to content

Crash while using Randomizer Mod #92

Open

Description

@ThatGreenAlien

I really appreciate your work so far on this! I started playing with this Randomizer Mod: https://www.nexusmods.com/bloodborne/mods/15

I wasn't able to figure out how to get the mod to work with the app (it seems to want me to just overwrite the original files, so I backed up the original and did so). It worked great up until I got to the point in Central Yharnam where the guy is banging on the door, a little past there on the other side of the gate next to him. I'm now not able to load that save file without it crashing.

Truthfully I have no idea if this has to do with the randomizer or not, but I'm able to start a new file and the game runs fine at that point (although I haven't tested getting to that same point in the game).

Bloodborne for Mac 0.5.9: crash report

  • Mac: Mac16,13 (Apple M4), 24 GB, macOS 15.7.9 (Build 24G830)
  • Settings: output 1280x720, upscaler off, cap 60 FPS, fixed timing, windowed
  • Session: started 2026-10-26 19:46:52 -06:00, ran 0 min 43 s
  • Exit status: 139
  • Cause: the game crashed (signal 11 at guest offset 0x518c6d) (at 19:47:36.222)
  • Log: game-2026-10-26_19-46-52.log, 536 lines: 1 critical, 1 error, 5 warnings
Warnings and errors before the cause (5 most recent)
19:46:55.476 WARN   GPU [Render.Vulkan] <Warning> vk_pipeline_serialization.cpp:390 LoadPipelineStage: Cached permutation 0 of fs_fbe7c4b6 conflicts with index 1, skipping preload
19:46:55.542 WARN   GPU [Render] <Warning> vk_pipeline_serialization.cpp:511 WarmUp: 1 cached pipelines could not be preloaded; they compile when used
19:47:03.056 WARN   GPU [Lib.AvPlayer] <Warning> avplayer_source.cpp:308 Stop: Could not stop playback: already stopped.
19:47:12.572 WARN   == Stall during rendering at flush 1
19:47:18.376 WARN   == Stall during rendering at flush 306
game-2026-10-26_19-46-52.log (69 lines around the cause)
19:47:32.585 INFO   Runtime: guest thread 'CSChrThread2' created (stack=65536, prio=700)
19:47:32.585 INFO   Runtime: guest thread 'CSChrThread2' affinity 0xf
19:47:32.585 INFO   Runtime: guest thread 'CSChrThread1' is host thread 652856, handle 0x805c4f810 (affinity 0xf, prio 700)
19:47:32.585 INFO   Runtime: guest thread 'CSChrThread3' created (stack=65536, prio=700)
19:47:32.585 INFO   Runtime: guest thread 'CSChrThread3' affinity 0xf
19:47:32.585 INFO   Runtime: guest thread 'CSChrThread3' is host thread 652858, handle 0x805c4f410 (affinity 0xf, prio 700)
19:47:32.585 INFO   Runtime: guest thread 'CSChrThread4' created (stack=65536, prio=700)
19:47:32.585 INFO   Runtime: guest thread 'CSChrThread4' affinity 0x30
19:47:32.585 INFO   Runtime: guest thread 'CSChrThread2' is host thread 652857, handle 0x805c4f610 (affinity 0xf, prio 700)
19:47:32.585 INFO   Runtime: guest thread 'CSChrThread5' created (stack=65536, prio=700)
19:47:32.585 INFO   Runtime: guest thread 'CSChrThread5' affinity 0x30
19:47:32.585 INFO   Runtime: semaphore id=72, attr=2, initial=0, max=1
19:47:32.585 INFO   Runtime: semaphore id=73, attr=2, initial=0, max=1
19:47:32.585 INFO   Runtime: guest thread 'CSChrThread4' is host thread 652859, handle 0x805c4f210 (affinity 0x30, prio 700)
19:47:32.585 INFO   Runtime: guest thread 'CSChrThread5' is host thread 652860, handle 0x805c4f010 (affinity 0x30, prio 700)
19:47:32.586 INFO   Runtime: guest thread 'CSChrBackInitialize1' created (stack=65536, prio=700)
19:47:32.586 INFO   Runtime: guest thread 'CSChrBackInitialize1' affinity 0x3e
19:47:32.586 INFO   Runtime: semaphore id=74, attr=2, initial=0, max=1
19:47:32.586 INFO   Runtime: semaphore id=75, attr=2, initial=0, max=1
19:47:32.586 INFO   Runtime: guest thread 'CSChrBackInitialize1' is host thread 652861, handle 0x805c4ee10 (affinity 0x3e, prio 767)
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread0' created (stack=65536, prio=700)
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread0' affinity 0xf
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread0' is host thread 652862, handle 0x805c4ec10 (affinity 0xf, prio 700)
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread1' created (stack=65536, prio=700)
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread1' affinity 0xf
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread1' is host thread 652863, handle 0x805c4ea10 (affinity 0xf, prio 700)
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread2' created (stack=65536, prio=700)
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread2' affinity 0xf
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread2' is host thread 652864, handle 0x805c4e810 (affinity 0xf, prio 700)
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread3' created (stack=65536, prio=700)
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread3' affinity 0xf
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread3' is host thread 652865, handle 0x805c4e610 (affinity 0xf, prio 700)
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread4' created (stack=65536, prio=700)
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread4' affinity 0x30
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread4' is host thread 652866, handle 0x805c4e410 (affinity 0x30, prio 700)
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread5' created (stack=65536, prio=700)
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread5' affinity 0x30
19:47:32.586 INFO   Runtime: guest thread 'CSClothThread5' is host thread 652867, handle 0x805c4e210 (affinity 0x30, prio 700)
19:47:32.698 INFO   Native ultrawide: observed scene depth 3840x1080 (no host scaling)
19:47:32.840 INFO   Runtime: open(/app0/dvdroot_ps4/map/m24/m24_9999.tpf.dcx) -> not found
19:47:36.222 CRIT   Crash: the game crashed (signal 11 at guest offset 0x518c6d)
19:47:36.222 INFO   Guest fault (signal 11) at guest offset 0x518c6d, address 0x0
19:47:36.222 INFO     rax=0xbe257277ca932000 rbx=0x700001e688 rdi=0x7135221ce0 rsi=0x6020 rsp=0x8064973e0
19:47:36.222 INFO     #2 0x0
19:47:36.223 INFO     #3 0x801ee2c97
19:47:36.223 INFO     #4 0x8013e412e
19:47:36.223 INFO     #5 0x800fe7125
19:47:36.223 INFO     #6 0x800f812b4
19:47:36.223 INFO     #7 0x800f80892
19:47:36.223 INFO     #8 0x80142c137
19:47:36.223 INFO     #9 0x80142da49
19:47:36.223 INFO     #10 0x80103d438
19:47:36.223 INFO     #11 0x80103d2c1
19:47:36.223 INFO     #12 0x801067579
19:47:36.223 INFO     #13 0x80103deff
19:47:36.223 INFO     #14 0x800f8a48c
19:47:36.223 INFO     #15 0x800f88ceb
19:47:36.223 INFO     #16 0x802018e74
19:47:36.223 INFO     #17 0x801e4a6f5
19:47:36.223 INFO     #18 0x8000000df
19:47:36.223 INFO     #19 ~/Desk
5D32
top/BB/Bloodborne.app/Contents/MacOS/bb-probe+0xaa3 (enter_on_stack)
19:47:36.223 INFO     #20 ~/Desktop/BB/Bloodborne.app/Contents/MacOS/bb-probe+0x25037 (probe_main.cold.67)
19:47:36.223 INFO     #21 ~/Desktop/BB/Bloodborne.app/Contents/MacOS/bb-probe+0x3af7 (probe_main)
19:47:36.223 INFO     #22 ~/Desktop/BB/Bloodborne.app/Contents/MacOS/bb-probe+0x24ba6 (game_thread)
19:47:36.223 INFO     #23 /usr/lib/system/libsystem_pthread.dylib+0x5e05 (_pthread_start)
19:47:36.223 INFO     #24 /usr/lib/system/libsystem_pthread.dylib+0x1857 (thread_start)
19:47:36.223 INFO   bbgpu-host: exiting: control port died (bb-probe exited)
19:47:36.223 INFO   Exit: pipeline archive flushed in 0 ms
19:47:36.395 ERROR  launcher: the game stopped with status 139 after 0 min 43 s

Activity

  1. Wooloomooloo2 commented on Nov 12, 2026

    @Wooloomooloo2
    Owner

    Thanks @ThatGreenAlien, and sorry for the slow reply. Overwriting the game's own files can break the game check and leaves no easy way back, so please:

    1. Restore the original files you backed up (or extract the game again).
    2. Update to 0.5.15, and add the randomizer through Mods & Cheats… in the launcher. The port then applies it on top of the untouched game.
    3. Try loading the save again.

    If it still crashes at the same point, please post the new crash report. Saves made with a randomizer can depend on its exact files, so it may also be worth asking the mod's author whether that spot is a known problem.

    Written with Claude Code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0