Skip to content

Ocarina of Time: note the Saria-cutscene GPU hang and the opt-in workaround on an M2 Air - #1994

Open
Mkhurana3 wants to merge 3 commits into
seedds:mainfrom
Mkhurana3:patch-1
Open

Mkhurana3 wants to merge 3 commits into
seedds:mainfrom
Mkhurana3:patch-1

Conversation

@Mkhurana3

@Mkhurana3 Mkhurana3 commented Nov 9, 2026 •

Copy link
Copy Markdown

What and why

Adds one "Open" bullet to Ocarina of Time's note (dm/games/0400486024DEC000/README.md) with what an M2 MacBook Air (16 GB) shows on the Saria-cutscene GPU hang tracked in #1326 (reported first as #1690, closed as a duplicate), and on the opt-in workaround in #1842. It changes no code and does not depend on #1842 being merged: the bullet says that switch is not on main.

Checked

  • Tests: none run; the change is one line in a game note (CI covers the docs build).
  • Games run, with title ID and version: Ocarina of Time 0400486024DEC000 v131072. The unfixed runs are six from the Saria autosave. With the switch, runs of about 8 min (render scale 1.0) and about 12 min (0.75). The off/on pair is about 90 s of the cutscene each. All numbers are from the host logs (timing up to frame, [longframe] and task / mesh pipeline lines).
  • Devices and OS: Apple M2 MacBook Air, 16 GB, macOS 27.2.
  • Measurements before and after: the off/on pair above; its limits are in the bullet.

Docs

  • The finding is in its game note. python3 dm/tools/docs_symptoms.py was not run: nothing was added to a docs/reference entry, only the game note.
  • A chain tool changed: not applicable.
  • No game files, keys or data extracted from a game in the change or the attachments

…k isolation on an M2 MacBook Air

Adds one "Open" bullet to the game's note. On an M2 MacBook Air (16 GB), 6 of 6 runs from the autosave just before Saria gives Link the ocarina died within 158-241 s on main 1794a35, in a GPU hang and then a revoked GPU. With DM_NVN_ISOLATE_TASK=1 from seedds#1842 (not on main) two runs of about 8 and 12 minutes had no ErrorHang. Over the same 3,600 frames of the cutscene at render scale 0.75, the switch took 4.5 ms (9 %) more GPU time a frame, one pair played by hand. The same runs show first-use compiles of the foliage task's pipelines of 7.0, 7.1 and 10.5 s, and two pipelines of task a7f22b4a795ff4d1 that failed with XPC_ERROR_CONNECTION_INTERRUPTED. Only the note changes: no code, no front-end action.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01964yimrHXRP82dKYhi1BKj
…ten windows match

The A/B windows show the whole +4.5 ms (9 %) GPU gap coming from two slow ON windows (ending at frames 1500 and 1800, one with pipeline compiles and one without); in the other ten the GPU p50 differs by about 0.01 ms each. The bullet now says that instead of giving the gap as the cost of the extra cuts.
@Mkhurana3 Mkhurana3 changed the title Ocarina of Time: note the Saria-cutscene GPU hang and the cost of task isolation on an M2 Air Ocarina of Time: note the Saria-cutscene GPU hang and the opt-in workaround on an M2 Air Nov 9, 2026
The a7f22b4a795ff4d1 XPC failures are a compiler crash already fixed on main (37f076a), per the maintainers on seedds#1326, and are not part of the hang. The three a5288d0a6c4971fd first-use compiles are explained by the task and its meshes being absent from the prebuilt mesh lists.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Documentation game: 0400486024DEC000 A game

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant