8000 Crash: the GPU stopped making progress (3002 ms) · Issue #106 · Wooloomooloo2/bloodborne_mac_port · GitHub
[go: up one dir, main page]

Skip to content

Crash: the GPU stopped making progress (3002 ms) #106

Closed

Description

@DarthInfinix

What were you doing when it happened?

Diagnostics: please drag crash-2026-10-29_16-02-41.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.11: crash report

  • Mac: Mac16,12 (Apple M4), 16 GB, macOS 27.2 (Build 26B118)
  • Settings: output 1920x1080, upscaler off, cap 60 FPS, fixed timing, full screen
  • Session: started 2026-10-29 16:02:41 05:30, ran 87 min 49 s
  • Exit status: 1
  • Cause: the GPU stopped making progress (3002 ms) (at 17:30:30.611)
  • Log: game-2026-10-29_16-02-41.log, 3137 lines: 2 critical, 3 errors, 29 warnings
Warnings and errors before the cause (5 most recent)
16:49:21.478 ERROR  GPU [Render.Vulkan] <Error> liverpool_to_vk.cpp:801 SurfaceFormat: Unknown data_format=15 and num_format=7: using a stand-in
16:53:09.093 WARN   == Stall during rendering at flush 130620
17:12:34.267 WARN   GPU [Lib.AvPlayer] <Warning> avplayer_source.cpp:308 Stop: Could not stop playback: already stopped.  (×4)
17:14:00.762 WARN   == Stall during rendering at flush 130768
17:20:53.451 WARN   GPU [Render.Vulkan] <Warning> emit_spirv.cpp:459 operator(): Float32 denorm flushing is not supported by the GPU
game-2026-10-29_16-02-41.log (13 lines around the cause)
17:30:15.226 INFO   Runtime: guest thread 'CSClothThread4' affinity 0x30
17:30:15.226 INFO   Runtime: guest thread 'CSClothThread5' created (stack=65536, prio=700)
17:30:15.226 INFO   Runtime: guest thread 'CSClothThread5' affinity 0x30
17:30:15.226 INFO   Runtime: guest thread 'CSClothThread5' is host thread 2556062, handle 0x8135dfe10 (affinity 0x7f, prio 700)
17:30:15.226 INFO   Runtime: guest thread 'CSClothThread4' is host thread 2556061, handle 0x8135e0010 (affinity 0x30, prio 700)
17:30:15.478 INFO   Runtime: open(/app0/dvdroot_ps4/map/m24/m24_9999.tpf.dcx) -> not found
17:30:15.849 INFO   Frame pool: new peak 177 of 256 KiB (69%), 47 of 216 records, frame 229562
17:30:18.517 INFO   Metal binary archive: wrote 1045 pipelines in 8082 ms; this session 925 from the archive, 6 compiled
17:30:30.611 CRIT   Crash: the GPU stopped making progress (3002 ms)
17:30:30.611 ERROR  STOP: GPU watchdog: tick 475858 committed, 475857 complete, no progress for 3002 ms; exiting so the GPU does not stall WindowServer (BB_GPU_WATCHDOG_MS)
17:30:30.712 INFO   GPU process: host lost (host process exited with status 75) while rendering; exiting
17:30:30.712 CRIT   Crash: the GPU process stopped unexpectedly (host process exited with status 75)
17:30:30.873 ERROR  launcher: the game stopped with status 1 after 87 min 49 s

Activity

  1. DarthInfinix commented on Oct 29, 2026

    @DarthInfinix
    Author
  2. added 2 commits that reference this issue on Oct 31, 2026
  3. Wooloomooloo2 commented on Oct 31, 2026

    @Wooloomooloo2
    Owner

    Thank you @DarthInfinix for the crash zip. The GPU watchdog ends the game if the GPU stops finishing work for 3 seconds, so a real GPU hang can't freeze the Mac's display. It judged progress only by notices that arrive on the CPU after the GPU finishes. On a busy 16 GB Mac those notices can lag behind, so it could count a delay as a GPU stall.

    0.5.12 includes #107 from @evill33t: the watchdog now also checks the GPU's own completion signal. Real stalls still end the game. Your log can't show which kind this was, so closing for now. If it happens again on 0.5.12, please reopen with the new crash zip. The log line now shows both counters (GPU event …, handlers …), which will tell us.

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