8000 Crash: the game stopped responding (no new frame for 30 seconds, 225697 frames before; BB_HANG_SE · Issue #144 · Wooloomooloo2/bloodborne_mac_port · GitHub
[go: up one dir, main page]

Skip to content

Crash: the game stopped responding (no new frame for 30 seconds, 225697 frames before; BB_HANG_SE #144

Open

Description

@andel0

What were you doing when it happened?

Diagnostics: please drag crash-2026-11-08_14-11-18.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.14: crash report

  • Mac: Mac16,1 (Apple M4), 16 GB, macOS 26.6.2 (Build 25G83)
  • Settings: output 1920x1080, upscaler off, cap 40 FPS, variable timing, full screen
  • Session: started 2026-11-08 14:11:18 01:00, ran 94 min 45 s
  • Exit status: 76
  • Cause: the game stopped responding (no new frame for 30 seconds, 225697 frames before; BB_HANG_SECONDS) (at 15:46:03.541)
  • Log: game-2026-11-08_14-11-18.log, 1248 lines: 1 critical, 1 error, 287 warnings
Warnings and errors before the cause (5 most recent)
15:30:27.384 WARN   GPU [Render] <Warning> mtl_draw_core.mm:323 ReportSkips: Metal draws skipped in the last 5 s: empty scissor 1442
15:30:32.409 WARN   GPU [Render] <Warning> mtl_draw_core.mm:323 ReportSkips: Metal draws skipped in the last 5 s: empty scissor 4961
15:30:37.434 WARN   GPU [Render] <Warning> mtl_draw_core.mm:323 ReportSkips: Metal draws skipped in the last 5 s: empty scissor 2485
15:40:29.497 WARN   == Stall during rendering at flush 165958
15:40:56.392 WARN   == Stall during rendering at flush 167025
game-2026-11-08_14-11-18.log (12 lines around the cause)
15:46:03.541 INFO     EzWorkPool_TypeB1        blocked in condvar (0x71091009b0) for 30337 ms; __psynch_cvwait 0xa<cond_wait 0xcc<2083ecd<207e9e8<208bfe5<20340ab<263b246<host_start 0xa9<_pthread_start 0x73<thread_start 0xf
15:46:03.541 INFO     EzWorkPool_TypeA3        blocked in condvar (0x71091007b0) for 116241 ms; __psynch_cvwait 0xa<cond_wait 0xcc<2083ecd<207e9e8<208bfe5<20340ab<263b246<host_start 0xa9<_pthread_start 0x73<thread_start 0xf
15:46:03.541 INFO     EzWorkPool_TypeA2        blocked in condvar (0x7109100610) for 116241 ms; __psynch_cvwait 0xa<cond_wait 0xcc<2083ecd<207e9e8<208bfe5<20340ab<263b246<host_start 0xa9<_pthread_start 0x73<thread_start 0xf
15:46:03.541 INFO     EzWorkPool_TypeA1        blocked in condvar (0x7109100470) for 116242 ms; __psynch_cvwait 0xa<cond_wait 0xcc<2083ecd<207e9e8<208bfe5<20340ab<263b246<host_start 0xa9<_pthread_start 0x73<thread_start 0xf
15:46:03.541 INFO     EzWorkPool_TypeA0        blocked in condvar (0x71091002d0) for 116241 ms; __psynch_cvwait 0xa<cond_wait 0xcc<2083ecd<207e9e8<208bfe5<20340ab<263b246<host_start 0xa9<_pthread_start 0x73<thread_start 0xf
15:46:03.541 INFO     FD4JobWorker:0           blocked in semaphore (0x13) for 5681283 ms; __psynch_cvwait 0xa<sem_wait 0x247<263ae6a<106747f<263b246<host_start 0xa9<_pthread_start 0x73<thread_start 0xf
15:46:03.541 INFO     Core.Logging.BackgroundStrategy blocked in semaphore (0x12) for 5681296 ms; __psynch_cvwait 0xa<sem_wait 0x247<263ae6a<26471c5<263b246<host_start 0xa9<_pthread_start 0x73<thread_start 0xf
15:46:03.541 INFO     main                     running; 21b8890<23008cc<1f77d54<1d9b37b<1d9cd79<103d438<103d2c1<1067579<103deff<f8a48c
15:46:03.541 CRIT   Crash: the game stopped responding (no new frame for 30 seconds, 225697 frames before; BB_HANG_SECONDS)
15:46:03.541 INFO   bbgpu-host: exiting: SIGTERM
15:46:03.541 INFO   Exit: pipeline archive flushed in 0 ms
15:46:04.087 ERROR  launcher: the game stopped with status 76 after 94 min 45 s

Activity

  1. Wooloomooloo2 commented on Nov 8, 2026

    @Wooloomooloo2
    Owner

    Thanks @andel0. This looks like it could be the long-session freeze we fixed in 0.5.14 (#127), so it's important to find out whether it's the same thing or something new. Could you attach crash-2026-11-08_14-11-18.zip (the launcher showed it in Finder; it's also in ~/Library/Logs/Bloodborne/Reports)? The full log shows whether the game's per-frame memory filled up again (the "Frame pool" lines).

    Your settings (40 FPS cap, variable timing) differ from the ones we tested the fix with (60 FPS, fixed timing), so we're running a long session with yours now. Until then, quitting and restarting about every 80 minutes avoids the freeze.

  2. andel0 commented on Nov 9, 2026

    @andel0
    Author

    Attached all three hangs from 0.5.14 (14:11, 17:43, 18:14). Settings were 40 FPS, variable timing, 1080p. One later session with 60 FPS fixed timing ran 75 minutes without a hang.

    crash-2026-11-08_14-11-18.zip

    crash-2026-11-08_17-43-36.zip

    crash-2026-11-08_18-14-05.zip

  3. Wooloomooloo2 commented on Nov 12, 2026

    @Wooloomooloo2
    Owner

    Thanks @andel0, all three logs helped. This is not the long-session freeze fixed in 0.5.14 (#127): the per-frame memory that filled up there stays almost empty in all three of your sessions (at most 11 of 256 KiB).

    What the logs show instead: in each hang the game's main thread is still running rather than waiting, and the render thread waits for it, so the main thread seems to be stuck in a loop. All three were at a 40 FPS cap. A 40 cap has no fixed-step patch, so the game runs with variable timing there, and your 60 FPS fixed-timing session ran without a hang. The same pattern also shows up in an older log of ours with the same settings, so it isn't new in 0.5.14.

    Until it's fixed, a 60 FPS cap with fixed timing is the setting to use. We'll try to reproduce it here with your settings; it hung after 8 minutes once, which helps.

    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