macos m2 max sequoia 15.1.1 (24B91)
in battlenet download settings, I have disabled the auto update, and restricted the update to 4am, but it doesn’t help.
hmm, seems the game crashed with EXC_BAD_ACCESS, and the update battlenet shows is probably fake.
In version 2.8.0.99920, the issue has gotten worse. Previously, it happened 2 to 4 times of 12 hours play (estimated), but in this version, it occurs so frequently that I almost give up this game.
same. about every 20 min +/- . game freezers and quits, I get a notice for an update.
76B82FD2-E24D-4405-ADA8-4F5A7235FA66
and another
EC17710D-DE8A-430D-B9D1-E87C35654608
Me too, game freezes, then quits to desktop after about five seconds, battle.net then updates diablo3, no error message, or report unexpected application crash option comes up, so the OS doesn’t think that there wasn’t a problem.
Managed to have Console running for a crash, didn’t get anything blindingly obvious, this is the only error message that stuck out.
delegate_identifier:Performance Diagnostics__:::__message:Synchronous URL loading of should not occur on this application’s main thread as it may lead to UI unresponsiveness. Please switch to an asynchronous networking API such as URLSession.
Had four of those in a row, all identical. And just in case, the last error message from the Diablo3 application.
RBSStateCapture remove item called for untracked item 424-360-2053064 (target:[app<application.DiabloIII.app.B4170014-0EA2-4BE7-B5E0-9F42C060DEF6(501)>:22738])
At the moment the crashes are frequent enough that I cannot get the Season’s Set Items because I cannot complete those things where you have to do five quests in a row in each chapter because it’ll crash after having only done 2-4.
Two more attempts to finish an act cache for the season and twice more crashed at bounty 3 and 4, futile.
I got the game to launch once after the 2.0.0 update, played a bit no issues, but now the game will not even load a game, I click on a toon, entering game, downloading additional content shows then immediate crash to desktop, no error report shows at all.
Still doing it, it’s been over a week, I understand these things take time but all we really need is an official post stating that they know about the issue and are looking into it. Remember this issue doesn’t just slow down gameplay or make playing more annoying, it literally makes things like getting the season set impossible due to completing season achievements been impossible.
This is such a MASSIVE issue for all Mac Users. I hope the developers take it seriously and create a better patch asap, the game got less stable after the last Mac update they did. The game crashes every 20 min on every Mac we have tried. In other words the game is totally unplayable on Mac at the moment.
The last straw that broke my spirit was that it just killed my top Seasonal HC character (which I had tons of game time in) during a crash, and it also crashed my friends game so his HC character died in the same group play. We have reported this to Blizzards tech support with the crash logs hoping for a rollback, but its so sad that there is no way to enjoy the game anymore on Mac OS (if you don’t use a Virtual Machine running Windows). I’ll use a VM moving forward so bad things like this does not happen again.
Regards, Very Very Sad Mac User
Sorry for Hardcore loss, I’ve been very fortunate, it’s never gotten me killed, even when it crashed when I was in combat that I’d definitely die to without intervention. I’m always just back in town. I see the version number of Diablo3 has changed so I’m gonna give it another shot and I’ll report back.
EDIT: Forget all that I was looking at the Public Test Realm I just installed to check that out, not that it really matters because I’m only interested in the main game but the Public Beta is even worse, every login attempt before getting to menus it says there is a new patch and Diablo 3 has to restart to apply it, and there is never a new patch.
same, iv crashed during rifts, just before getting cashes. sometimes I get an hour, usually 2 -3 crashes per. HELLO!
EDIT #1: Added clarity on how to ensure that Diablo III and Battle.net are NOT running.
EDIT #2 (February 27, 2025): Diablo 3 crashed twice on me yesterday. I added a tweak to the permissions guide. The entire permissions fix, including the added tweak, got me back up and running!
Hey All,
Repeated crashing like this and an update to Diablo III is most likely due to patch looping—which means that the permissions are not set correctly for Diablo III . I’ve posted a few times with solutions that seem to work; so I’ll post the guide again 
However, before you follow the guide for fixing the permissions, I highly recommend NOT allowing Spotlight to index the Diablo 3 folder as it can cause slow downs and possibly crashing as well.
The following are instructions to stop Spotlight from indexing the Diablo 3 folder in macOS Monterey 12.7.6.
1.) While the Finder is active, click the Apple menu at the top left of the screen.
2.) Click System Preferences (System Settings for macOS Ventura and later).
3.) Click Spotlight and then click the “Privacy” tab.
4.) Click the “+” button at the bottom left, and then click on the drop down box at the top and click on your hard drive that contains the Diablo 3 folder (it’s usually called Macintosh HD).
5.) Double click the “Applications” folder to open it within that window and then select the Diablo 3 folder (by clicking on it once). Then click the “Choose” button at the bottom right, and the Diablo 3 folder should be listed as one of the locations that Spotlight will prevent from searching.
The end-objective we want for the above instructions is to prevent Spotlight from indexing the “Diablo 3” folder, which is in the “Applications” folder.
As of February 27, 2025 I’m on an M1 iMac running Sequoia 15.3.1 and playing Diablo 3 as native Apple silicon (these instructions should also fix permissions even if you run Diablo 3 in Rosetta).
Try these steps to fix the permissions on the “Diablo III” folder: On a macOS administrator account (I’ve always played Diablo 3 on an administrator account) do the following:
Before the permission steps below, make sure that Diablo III and Battle.net applications are NOT running.
To ensure that Diablo III and Battle.net applications are NOT running, quit both of the applications and then (instructions for macOS Sequoia 15.3.1. Exact instructions may differ on previous operating systems):
1.) While the Finder is active, go to Go menu > Utilities > Open “Activity Monitor” application.
2.) While Activity Monitor is active, click on the “CPU” tab at the top of Activity Monitor’s window. It’s to the left of the “Memory” tab.
3.) While Activity Monitor is active, go to View menu > Columns > select “% CPU” (make sure there is a check mark next to “% CPU”). Then click on “Process Name” sort tab in Activity Monitor’s window to sort processes as descending (alphabetical order starting at top) by “Process Name” (the caret to the right of “Process Name” should be pointing up).
4.) While Activity Monitor is active, go to View menu > select “All Processes”
5.) Then go back into the View menu > select “Filter Processes”
6.) Then type the word “Agent” (without the quotes) within the Filter Processes box. A list of all loaded processes will populate that include the word “Agent”.
7.) The process you are looking for has the name “Agent” with the “Battle.net” app icon to its left. Select this process, and ONLY this process, by clicking on it once. Then go to View menu > select “Quit Process”. A window will pop up asking “Are you sure you want to quit this process?”. Click on “Force Quit”.
8.) Repeat steps 5 through 7 for “Diablo III” if, and ONLY if, “Diablo III” is still open for some reason after quitting it (meaning it is hanging).
9,) Quit Activity Monitor
Then, Quit ALL other applications that may be open:
Hold down Command (keep holding it) and hit Tab once > select any applications that may be open and Quit them; only the Finder should be active) then Restart the computer.
After the computer restarts, make sure there are NO other applications open (hold down Command (keep holding it) and hit Tab once > select any applications that may be open and Quit them; only the Finder should be active).
If you’re on an M series Mac, confirm that the “Diablo III” application is running natively on Apple Silicon:
1.) While the Finder is active, go to Go menu > Applications > Open the “Diablo III” folder.
2.) Select the “Diablo III” application (NOT the “Diablo III Launcher” application) by clicking on it once.
3.) While the “Diablo III” application is selected, get info on it by going to the File menu in the Finder > Get Info
4.) With the “Diablo III Info” window active, open General drop down (do this only if the General drop down is not already open), and make sure that there is NO CHECK MARK to the left of “Open using Rosetta”. Also make sure that there is NO CHECK MARK to the left of “Locked”.
If you’re on an Intel Mac, confirm that the “Diablo III” application is NOT locked:
1.) While the Finder is active, go to Go menu > Applications > Open the “Diablo III” folder.
2.) Select the “Diablo III” application (NOT the “Diablo III Launcher” application) by clicking on it once.
3.) While the “Diablo III” application is selected, get info on it by going to the File menu in the Finder > Get Info
4.) With the “Diablo III Info” window active, open General drop down (do this only if the General drop down is not already open), and make sure that there is NO CHECK MARK to the left of “Locked”.
For BOTH Intel and M series Macs, confirm that the “Diablo III Launcher” application is NOT locked:
1.) While the Finder is active, go to Go menu > Applications > Open the “Diablo III” folder.
2.) Select the “Diablo III Launcher” application (NOT the “Diablo III” application) by clicking on it once.
3.) While the “Diablo III Launcher” application is selected, get info on it by going to the File menu in the Finder > Get Info
4.) With the “Diablo III Launcher Info” window active, open General drop down (do this only if the General drop down is not already open), and make sure that there is NO CHECK MARK to the left of “Locked”.
1.) While the Finder is active, go to Go menu > Applications > Select the “Diablo III” folder (by clicking on it once)
2.) While the “Diablo III” folder is selected, get info on it by going to the File menu in the Finder > Get Info
3.) With the “Diablo III Info” window active, open Sharing & Permissions drop down (do this only if the Sharing and Permissions drop down is not already open), and click on the lock at the bottom right.
4.) When you click on the lock at the bottom right, a dialogue prompt will come up stating “Finder wants to change permissions on “Diablo III”. Then authenticate with your password and click the “OK” button.
5.) Make sure that ALL “Names” in the Sharing & Permissions drop down for the “Diablo III” folder has their “Privilege” set to “Read & Write” (I have three “Names”: my account name, admin, and everyone), then click the “Read & Write” Privilege next to the “everyone” Name and switch it to “Read Only”. Then, IMMEDIATELY switch it back to “Read & Write” (this forces macOS to ‘sense’ a permissions change).
5A.) Confirm macOS ‘sensed’ this change by clicking the drop down button underneath that has 3 dots in a circle. You should see 2 options:
1.) “Apply to enclosed items…”
2.) “Revert changes”
The second option, “Revert changes”, should NOT be greyed out (it should be in black), which indicates that macOS has actually ‘sensed’ the permissions have changed (DO NOT click on “Revert changes”, this step is simply used as a visual confirmation).
5B.) Click the drop down button underneath that has 3 dots in a circle (it should already be open) and select “Apply to enclosed items…”, another dialogue box comes up asking if you are sure you want to apply this action, then click “OK”.
6.) Now do the same process on the “Battle.net” folder. While the Finder is active, go to Go Menu > Computer > open the volume where you play Diablo III from, its usually titled Macintosh HD > Users > Shared
7.) Select the “Battle.net” folder in the Shared folder and repeat the process in steps 5, 5A, and 5B above, but for the “Battle.net” folder.
8.) Close all windows in the Finder, then open the “Applications” folder, and open “Battle.net” application.
9.) Do a “Scan and Repair” on Diablo III and WAIT for it to completely finish before you click the “Play” button. Also, whenever Diablo III is updated, WAIT for it to completely update, before clicking the “Play” button. Waiting for completion before playing helps ensure that there isn’t any data corruption with the game files. I have had to reset the permissions like this on the “Diablo III” and “Battle.net” folders after every update to the macOS operating system, and you may have to as well.
10.) Click “Play” to launch the game.
1.) Write down or take a screen shot of your current in-game video settings (I took a screen shot before the 2.7.8 PTR for personal reference )
2.). Set the following in-game video options to these settings:
Display: Windowed (Fullscreen) [I always play in Windowed (Fullscreen), because it allows me to tab out to other apps] Also, Diablo 3 would usually crash at some point for me while in Fullscreen, so I highly recommend playing in Windowed (Fullscreen).
Lock Cursor: Checked
Max Foreground FPS: 60
Max Background FPS: 8
Large Cursor: Checked
Texture Quality: Low
Shadow Quality: Off
Physics: Low
Clutter Density: Off
Anti-Aliasing: None
Low FX: Checked
Then click “Apply” button and click either “Accept” or “OK”, whichever pops up.
Basically, just put all video settings as low, play for a while, then increase video settings as desired to see if it’ll work well.
Hope this helps
If you have more issues, let me know, I’ll do my best to help out.
Nope, none of those fixed, thank you for the effort though, it still can only get to the character screen, can pick and start game, gets all the way till I can hear the startup sound entering the game, and crashes to desktop, even fully cleaned out and reinstalled Battlenet app and game.
No apple error report shows when crashes. and the D3 DeBug shows
2025.02.14 19:09:48.741781360 ChannelHandler::_OnSetChannelAttributes failure. error=3006 request= state_change { attribute { name: “D3.Party.JoinPermission” value { int_value: 3 } } }
2025.02.14 19:09:48.741891197 >>> Sabine BnetPartyState::SetAttribute_Callback key=D3.Party.JoinPermission token=27 callback_code=3006
2025.02.14 19:09:48.745959293 ERROR: >>> Sabine BnetPartyState::SetPrivacyLevel code=3006
2025.02.14 19:09:48.746256010 ChannelHandler::_OnSubscribeChannel failure. error=3006 request=channel_id { high: 432345570262123805 low: 11882024915555064574 } object_id: 6
2025.02.14 19:09:48.750262813 ChannelHandler::_OnSetChannelAttributes failure. error=3006 request= state_change { attribute { name: “D3.Party.GameCreateParams” value { message_value: “\010\002\020\200\200P\032\026\010\000\025\224V\001\000\030\036"\007\010\000\020\314\270\375I8\000H\t*\006Sabine0\000” } } }
2025.02.14 19:09:48.818429261 >>> Sabine BnetPartyState::SetAttribute_Callback key=D3.Party.GameCreateParams token=29 callback_code=3006
2025.02.14 19:09:49.007983059 ERROR: >>> Sabine SetMyPartyGameParams_SetAttribute_GameCreateParams code=3006
2025.02.14 19:09:49.193302589 ERROR: >>> Sabine SetMyPartyGameParams_SetAttribute_GameCreateParams code=3006
Some perspective: I’m in your boat with no inside information but from the forums and my experiments it is mostly clear that macOS Catalina and Sequoia users are frustrated. Catalina users are all out of service, and Ventura and Sequoia users report frequent crashing. I personally can play a highly compromised game on an old 2015 MacBook running Monterey, which might be your best hope. Some skilled users I can only describe as hackers themselves have found workarounds but they’re not communicating clearly as to how to execute those ( I tried editing Info.plist and …no dice ).
It really does appear that the concern is met with a wall of negligent silence from official support, and it’s another diss to the users. After all the fix is simple just modify the (). Basic noob-coder stuff. But… careful you don’t diss them back you might get met with …more NOTHING
Hey tunaworks,
Thank you for your reply and sorry to hear it’s not working.
May I ask what hardware and operating system you are running? As far as I know, there have been issues with the game running on Intel Macs and operating systems older than Big Sur. I switched to an M series iMac in 2021 and haven’t had any serious issues with the game that I couldn’t fix. I’m currently running Diablo 3 in native Apple Silicon on an M1 iMac running macOS Sequoia 15.3.1.
Regardless of your hardware and operating system, there are other options you can do to try and get it to run.
First: Let’s rule out potential hardware issues.
1.) Unplug all unnecessary hardware accessories that may be attached to your computer such as external disk drives, USB thumb drives, Thunderbolt docks, etc. Only use the original keyboard and mouse that came with the computer (if possible). For example, I use the original Bluetooth Magic Keyboard with Touch ID and Numeric Keypad and Bluetooth Magic Mouse (the one with the Lightning Cable charging port) that came with the iMac M1. I have nothing else connected to the computer when playing Diablo 3.
2.) I highly recommend running Apple Diagnostics to test your Mac’s hardware for potential issues. I really want to post the link for instructions on how to perform this, however, I’m not sure if posting this link will violate Blizzard’s Forum’s Code of Conduct (I just read the Code of Conduct and it’s unclear to me).
So, make a backup of your data through your preferred backup means. Then search the web for “Use Apple Diagnostics to test your Mac”. Then click the link that is associated with the official Apple website and follow the instructions in that support article.
if you’re uncomfortable with performing the hardware test, then skip it.
Second: Let’s rule out any potential operating system and third-party software issues.
1.) Boot into Safe Mode to check the startup disk and repair any directory issues if needed. Search the web for “Start up your Mac in safe mode” and click on the official Apple support article and follow its instructions. After you’ve booted into safe mode, you can restart into normal mode (no need to log in). Diablo 3 may not work at all in Safe Mode. Can skip this step if you’re not comfortable with it
2.) Update macOS to the latest available operating system that your Mac can run. I understand that you may not be willing to based on needed apps, features, etc. of the macOS operating system you’re currently running. If so, skip this step.
3.) Uninstall all antivirus and Mac cleaning programs that you may have. I don’t run any of these.
4.) Uninstall “Diablo III” using the Battle.net app and confirm the “Diablo III” folder has been deleted from the “Applications” folder (if it’s still there after this step, please let me know, it shouldn’t be).
5.) Create a new administrator account on macOS to rule out any potentially conflicting User Login items and/or files on your original administrator account. Make sure there are no User Login items running in the newly created administrator account:
On macOS Sequoia 15.3.1 and while the Finder is active, go to the Apple Menu at the top left of your screen>System Settings>General>Log In Items & Extensions. Make sure there are NO items listed that will open automatically when you log in (if there are items listed, then left click once on them and then hit the “-” sign to remove them).
Third: Let’s reinstall Diablo III.
1.) Open the “Battle.net” app and reinstall “Diablo III” making sure to WAIT for it to completely finish before clicking the “Play” button (to avoid data corruption).
2.) After it’s completely done installing, click “Play” and wait for it to load completely.
3.) While in Diablo 3 menu, hit escape and click on “Options” and change the video settings display to “Windowed (Fullscreen)”. In the past there were issues with the “Fullscreen” setting (crashing/lagging/etc.).
4.) Play the game and enjoy!
EDIT: Added clarity to the Safe Mode instructions: After you’ve booted into safe mode, you can restart into normal mode (no need to log in). Diablo 3 may not work at all in Safe Mode.
Hey TheCyclo
Running an intel chip I mac
3 GHz 6-Core Intel Core i5
Radeon Pro 560X 4 GB
8 GB 2667 MHz DDR4
Sequoia 15.3.1 (24D70)
have been using macs since my first 512k Extended, yep I am old.
Never had an issue running D3 until the last D3 update. Have done most that you suggest, will try the rest.
Well went through all and everything checked out fine.
I am starting to think they did something for Apple silicone and broke what has been working on intel. Guess this is the universe saying it’s time to just stop playing a game I have had since day one.
Same here tunaworks, the last update screwed us — Running 15.3.1, on an M2 Ultra Mac fully juiced with memory. It’s pretty disappointing that they are not addressing it or letting us know that they are at least attempting a fix. Putting in a service ticket just gave me the run around. Kinda sad…
Hey tunaworks,
Thank you for posting your specs. Another big thank you for going through all the other options I posted to try to get it to work! I know it’s not the result you wanted, but at least we now know that all of those options do not work for you.
Just realized as I’m typing this that there are 2 other options for you:
1.) In my post with the permissions fix where it states “Before the steps below, make sure that Diablo III and Battle.net applications are NOT running.”, I will add some clarity on how to make sure that they are indeed no longer running (Battle.net can sometimes hang after closing).
2.) Since you are on Intel, there may be another/correct solution for your situation. There is another post in the Mac Technical Support forum that addresses an issue with Diablo 3’s “Info.plist” file. You may want to try that guide if all else fails.
Hope you get back up and running again!
Hey Featherstorm,
Interesting that you’re still having trouble on an M series Mac. I’m currently playing Diablo 3 on an M1 iMac running Sequoia 15.3.1.
Have you tried the Spotlight, Permissions, and Video Options guide I posted earlier in this thread (post #11, I edited some of it for clarity)?
I still get trouble with permissions here and there, but I just follow the instructions in the guide I posted and I’m back up and running.
At the very least, I highly recommend setting your in-game video options display to Windowed (Fullscreen). In the past there was crashing/lag/slow downs with the Fullscreen option.
After the character screen loads, hit Escape > Options > Video > Display: Windowed (Fullscreen). Then click “Apply” and then click either “OK” or “Accept” (whichever comes up).
Have you tried the other list of options I mentioned in post #14?
As far as I know, the “Info.plist” issue that was tackled by others in another Mac Technical Support thread, is mainly for Intel Macs. Might be worth a look into in that thread, though.
Other than that, hope you get up and running soon
FYI here is the error in the bug report file
<BlizzardError.Summary:>
EXC_BAD_ACCESS (KERN_INVALID_ADDRESS at 0x428A72204317A6FC)
<:BlizzardError.Summary>
<BlizzardError.Assertion:>
EXC_BAD_ACCESS (KERN_INVALID_ADDRESS at 0x428A72204317A6FC)
Thread 0x00000103 "Main Thread" [Stack Base: 0x000000016D29C000 Used Space: 13488/67092480 bytes]
0 0x0000000102CFD800 "Diablo III" FT_Stream_OpenBzip2 + 329268
1 0x0000000102D015E8 "Diablo III" FT_Stream_OpenBzip2 + 345116
2 0x0000000102D02A5C "Diablo III" FT_Stream_OpenBzip2 + 350352
3 0x0000000102D0914C "Diablo III" FT_Stream_OpenBzip2 + 376704
4 0x00000001039A7A8C "Diablo III" blizzard_core_catch_exception_raise + 9919264
5 0x000000010383FC8C "Diablo III" blizzard_core_catch_exception_raise + 8445216
6 0x00000001031CB864 "Diablo III" blizzard_core_catch_exception_raise + 1677560
7 0x0000000102B67E04 "Diablo III"
8 0x0000000102D34924 "Diablo III" FT_Stream_OpenBzip2 + 554840
9 0x00000001968E190C "com.apple.Foundation" __NSFireTimer + 104
10 0x00000001956F2394 "com.apple.CoreFoundation" __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 32
11 0x00000001956F2038 "com.apple.CoreFoundation" __CFRunLoopDoTimer + 1012
12 0x00000001956F1B48 "com.apple.CoreFoundation" __CFRunLoopDoTimers + 356
13 0x00000001956D7530 "com.apple.CoreFoundation" __CFRunLoopRun + 1856
14 0x00000001956D6734 "com.apple.CoreFoundation" CFRunLoopRunSpecific + 588
15 0x00000001A0C45530 "com.apple.HIToolbox" RunCurrentEventLoopInMode + 292
16 0x00000001A0C4B348 "com.apple.HIToolbox" ReceiveNextEventCommon + 676
17 0x00000001A0C4B508 "com.apple.HIToolbox" _BlockUntilNextEventMatchingListInModeWithFilter + 76
18 0x000000019924E848 "com.apple.AppKit" _DPSNextEvent + 660
19 0x0000000199BB4C24 "com.apple.AppKit" -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688
20 0x0000000199241874 "com.apple.AppKit" -[NSApplication run] + 480
21 0x0000000199218068 "com.apple.AppKit" NSApplicationMain + 888
22 0x0000000102D360D0 "Diablo III" FT_Stream_OpenBzip2 + 560900
23 0x0000000195270274 "com.apple.darwin.ignition" start + 2840
<:BlizzardError.Assertion>
I did this, followed your nice guide, but sadly game crashed again after 20 min or so. Today it even crashed as I was running around town, that’s a first. NGNGGH!!
I see Blizzard noticing the game doesn’t launch for some Mac users, but they need to address this issue too 
Playing on a Mac Studio M2, with Sequoia 15.3.1