Repository navigation
Closed as not planned
Closed as not planned
Copy link
Description
What were you doing when it happened?
Diagnostics: please drag crash-2026-11-05_19-40-46.zip (the launcher showed it in Finder) onto this issue: it has the full session log and macOS's crash reports.
Bloodborne for Mac 0.5.12: crash report
- Mac: Mac15,3 (Apple M3), 16 GB, macOS 26.6.2 (Build 25G83)
- Settings: output 1280x720, upscaler off, cap 60 FPS, fixed timing, windowed
- Session: started 2026-11-05 19:40:46 11:00, ran 104 min 50 s
- Exit status: 76
- Cause: the game stopped responding (no new frame for 30 seconds, 362818 frames before; BB_HANG_SECONDS) (at 21:25:36.275)
- Log: game-2026-11-05_19-40-46.log, 3146 lines: 1 critical, 194 errors, 498 warnings
Warnings and errors before the cause (5 most recent)
21:25:05.635 ERROR GPU [Render.Vulkan] <Error> vk_pipeline_common.cpp:58 Fail: Graphics pipeline fs_0x000000001c3953c6,vs_0x000000006a833138 not built (the Metal pipeline state failed): its draws are skipped (×2)
21:25:05.636 ERROR GPU [Render] <Error> mtl_pso_cache.mm:699 GetRenderPipeline: Metal render pipeline (vs 0xae0ea80be3a fs 0xaa3f846ea69): vertex attribute 0 (location 0) format Undefined has no Metal vertex format
21:25:05.636 ERROR GPU [Render.Vulkan] <Error> vk_pipeline_common.cpp:58 Fail: Graphics pipeline fs_0x00000000aa2a9925,vs_0x00000000adf9e624 not built (the Metal pipeline state failed): its draws are skipped (×2)
21:25:05.637 ERROR GPU [Render] <Error> mtl_pso_cache.mm:699 GetRenderPipeline: Metal render pipeline (vs 0xddc4cd56a6c fs 0x5278e64d9f8): vertex attribute 0 (location 0) format Undefined has no Metal vertex format
21:25:05.637 ERROR GPU [Render.Vulkan] <Error> vk_pipeline_common.cpp:58 Fail: Graphics pipeline fs_0x0000000052738b8a,vs_0x00000000ddbe557e not built (the Metal pipeline state failed): its draws are skipped (×2)
game-2026-11-05_19-40-46.log (12 lines around the cause)
21:25:36.274 INFO EzWorkPool_TypeB1 blocked in condvar (0x71091009b0) for 30566 ms; __psynch_cvwait 0xa<cond_wait 0xcc<2083ecd<207e9e8<208bfe5<20340ab<263b246<host_start 0xa9<_pthread_start 0x73<thread_start 0xf
21:25:36.274 INFO EzWorkPool_TypeA3 blocked in condvar (0x71091007b0) for 33454 ms; __psynch_cvwait 0xa<cond_wait 0xcc<2083ecd<207e9e8<208bfe5<20340ab<263b246<host_start 0xa9<_pthread_start 0x73<thread_start 0xf
21:25:36.274 INFO EzWorkPool_TypeA2 blocked in condvar (0x7109100610) for 33454 ms; __psynch_cvwait 0xa<cond_wait 0xcc<2083ecd<207e9e8<208bfe5<20340ab<263b246<host_start 0xa9<_pthread_start 0x73<thread_start 0xf
21:25:36.275 INFO EzWorkPool_TypeA1 blocked in condvar (0x7109100470) for 33454 ms; __psynch_cvwait 0xa<cond_wait 0xcc<2083ecd<207e9e8<208bfe5<20340ab<263b246<host_start 0xa9<_pthread_start 0x73<thread_start 0xf
21:25:36.275 INFO EzWorkPool_TypeA0 blocked in condvar (0x71091002d0) for 33454 ms; __psynch_cvwait 0xa<cond_wait 0xcc<2083ecd<207e9e8<208bfe5<20340ab<263b246<host_start 0xa9<_pthread_start 0x73<thread_start 0xf
21:25:36.275 INFO FD4JobWorker:0 blocked in semaphore (0x13) for 6285246 ms; __psynch_cvwait 0xa<sem_wait 0x247<263ae6a<106747f<263b246<host_start 0xa9<_pthread_start 0x73<thread_start 0xf
21:25:36.275 INFO Core.Logging.BackgroundStrategy blocked in semaphore (0x12) for 6285261 ms; __psynch_cvwait 0xa<sem_wait 0x247<263ae6a<26471c5<263b246<host_start 0xa9<_pthread_start 0x73<thread_start 0xf
21:25:36.275 INFO main running; swtch_pri 0xa<thread_yield 0x9<1067fc5<75b25e<76a8e5<420965<fd55d7<fd35a1<17f9e98<103d438
21:25:36.275 CRIT Crash: the game stopped responding (no new frame for 30 seconds, 362818 frames before; BB_HANG_SECONDS)
21:25:36.276 INFO bbgpu-host: exiting: SIGTERM
21:25:36.276 INFO Exit: pipeline archive flushed in 0 ms
21:25:36.570 ERROR launcher: the game stopped with status 76 after 104 min 50 s
Metadata
Metadata
Assignees
Labels
No labels
Activity
Wooloomooloo2 commentedon Nov 5, 2026
Thanks @instantcola. This is the same long-session hang as #127 (the game's per-frame memory fills up after about 1.5 to 2 hours of play; details there). Closing this as a duplicate so it's tracked in one place. Until it's fixed, quitting and restarting the game about every 90 minutes avoids it.
GPU: write occlusion query dumps in order with the draws (#127)
Wooloomooloo2 commentedon Nov 7, 2026
The cause of this freeze (the same as #127) is fixed in 0.5.14: long sessions no longer fill the game's per-frame memory. Thanks for the report.
GPU: write occlusion query dumps in order with the draws (Wooloomoolo…