Diablo IV consistently crashes to desktop after a few minutes on Apple Silicon (M1 Max, macOS Tahoe 26.5.2)

[pierrecathala]

Hello,
Hope you're doing well.

System Information
Mac: MacBook Pro 14" (2021)
Chip: Apple M1 Max
Memory: 32 GB
Operating System: macOS 26.5.2 (Tahoe)
D4Mac Version: 0.4.1 (9)
Wine Version: 11.0
Game Porting Toolkit: 3.0
Diablo IV: Latest version installed through Battle.net
Issue Description

The game launches successfully and is fully playable at first.

However, after a few minutes, Diablo IV suddenly closes and returns directly to the macOS desktop.

There is:

no Blizzard crash reporter,
no macOS crash dialog,
no entry in ~/Library/Logs/DiagnosticReports,
no visible error message.

Battle.net remains open after the game closes.

The crash timing is surprisingly consistent.

Troubleshooting already attempted

Removing the High Resolution Texture Pack.
Using AMD FSR 1.
Using AMD FSR 2.
Lowering all graphics settings.
Running with low textures.
Limiting FPS.
Various in-game graphics settings.

Interestingly, switching from FSR 1 to FSR 2 delays the crash by several minutes, but the game still eventually crashes.

This makes me suspect the problem may be related to rendering, memory management, Wine, D3DMetal, or GPTK rather than the game content itself.

Additional Information
The Mac is stable in every other application.
No kernel panic occurs.
No macOS crash report is generated.
The crash is an immediate return to desktop.
The problem is fully reproducible.

If there is any logging mode, debug build, or additional diagnostic information I can provide, I'd be happy to help.

Thank you for your work on D4Mac.

[kimlage]

I reproduced a very similar failure and have a candidate mitigation in draft PR #11.

Test environment:

• MacBook Pro, Apple M3 Max, 36 GB
• macOS 26.5.2
• D4Mac 0.4.1 (9), Wine 11.0, GPTK 3.0
• current Diablo IV build through Battle.net

Before the mitigation, Diablo IV exited abruptly four times after roughly 3-23 minutes. Battle.net remained open, with no Blizzard crash reporter, macOS crash dialog, or DiagnosticReports entry.

For an A/B run I quit D4Mac and relaunched it with both bundled recovery hooks disabled:

D4_KICK_DISABLE=1 D4_WATCHDOG_DISABLE=1 /Applications/D4Mac.app/Contents/MacOS/D4Mac

That session ran for more than 30 minutes without an abrupt exit. One world transition stalled for about five minutes, but the process remained alive, reconnected, and resumed without closing; the game was then exited normally.

The candidate is that D4Mac's legacy d4-kick/watchdog hooks remain armed on macOS 26.5+, even though CodeWeavers says its earlier workaround is no longer needed starting with Tahoe 26.5 (while both the CrossOver 26.1 Wine changes and macOS 26.5 Rosetta changes are required):

https://www.codeweavers.com/blog/mjohnson/2026/5/18/finally-diablo-iv-and-overwatch-are-playable-with-crossover-261-macos-265

Draft PR #11 applies that policy automatically on macOS 26.5+. A separately built patched app also launched the existing Battle.net bottle and Diablo IV installation successfully.

This is promising A/B evidence, not yet a complete root-cause proof, because the recoverable stall still occurred. If you test the environment-variable workaround, please report how long the session lasts and whether you see an abrupt exit versus a recoverable stall.

[pierrecathala]

Hi,

This completely solved the issue on my machine.

Since disabling the recovery hooks, I've been able to play for up to 1 hour and 30 minutes without a single crash or unexpected exit. In fact, I didn't encounter any issues at all during my test sessions.

It definitely looks like the legacy recovery hooks were responsible for the abrupt exits on macOS 26.5.2.

Thanks a lot for investigating this and for the quick fix!