Rosetta 2 Deadlock on M4 Pro

M3 Pro same same

Do you have a bug number for this?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Same problem on Mac mini M2 Pro

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits.

Bug Number: FB21838832

Thanks for that.

You only just filed this bug, so I’ve no news to share yet.

It looks like the CodeWeavers’ folks did a bunch of research into this. Do you know if they filed a bug about it?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

CodeWeavers already had an open bug for OverWatch 2, that same bug also affects Diablo2:Resurrected

I‘m also aware of another Rosetta2 bug they have open that affects legacy WoW clients.

Do you have FBnnn numbers for any of those?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

That would be FB15880492

I this now also affects Diablo 4 Test Realm/ that version might now be live with the Diablo 30th anniversary updates landing for both Diablo 4 & Diablo 2

I was just informed that FB21763885 might be more detailed and more easily reproducible.

That would be FB15880492

I was just informed that FB21763885

Perfect. Thanks!

I took a quick look as these and they definitely landed in the right place. Beyond that, there’s no much more info that I can share [1].

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] As I explain in Quinn’s Top Ten DevForums Tips, Apple folks can’t talk about The Future™.

Same issue on M1 Max with macos 15.7.4 on Diablo 2 resurrected

Same on M1 Pro, 26.2 (25C56)

Rosetta 2 Deadlock on M5

January 2026 Blizzard update causes a deadlock in Rosetta 2 on M4 chips. CodeWeavers (the developer of CrossOver) has analyzed the issue and identified it as a Rosetta translation failure, not a CrossOver application-level bug.

Hardware: M5 Mac Book Pro

System: Tahoe 26.2

Impacted Software:

CrossOver 25.1.1 Diablo II: Resurrected

Does this mean that the team working on Rosetta 2 is aware of the bug, and addressing it? I understand that you cannot speak about the future, but can you speak to the here and now? Is it being worked on? Is there any way the community can support the team working on this bug? I understand this may not seem like a big issue in the grand scheme of things, but there is a large community of people who would really like this fixed. Thank you for all of your work.

Does this mean …

I pretty much meant what I wrote:

• In my assessment, the right people have seen this bug.
• There is nothing more I can say about its status.

There are strict limits as to how much I can talk about Apple’s internal processes, and this issue has definitely bumped into those limits.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"