I have a MacBook Pro w/ M3 Max, 36 gb ram… D3 crashes periodically and I have to hard reboot the Mac. Has happen 4 times in two days and only happens on 2.7.8 build. Crash reports auto-sent.
Any cause and/or resolution on this issue?
I am getting the same crashes on my macbook pro M3 Max. I have found that if I am in full screen mode it crashes and locks up the system, using a 3 finger swipe I can get to another desktop and then force quit D3 which means i don’t have to force reboot. I have tried experimenting in windowed mode and found it still crashes but the window just closes.
I am not getting any error reports to send though.
Having the same kind of issues on a new 16" MBP M4 Pro. I can juuuuuust last long enough for the game to start and then it like loses my external monitor for a second and then goes black. Like Mysterons said, I can use the swipe gesture on the track pad and force close it. But it’s basically not playable.
I found if I force Rosetta (right-click the Diablo III, choose Get Info, and check the box for Rosetta) it works much more smoothly. Performance is still pretty good; I can play at around 100fps on at 3840x2160 and high settings.
I’m really glad Blizzard is giving this game some love. Also hope they get the bugs worked out.
Hey All,
The crashing sounds like a permissions issue. I have a detailed guide to fixing permissions for Diablo 3 that I’m going to post again here. 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 (I forgot to mention that in the permissions guide).
The following are instructions to stop Spotlight from indexing the Diablo 3 folder in macOS Monterey 12.7.6 (I’m slowly upgrading to Sequoia and therefore I’m not quite familiar with Sequoia’s UI, so the exact navigation process may differ for you, but the end-objective is the same):
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.
Again, I’m not familiar with macOS Sequoia’s interface, but 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.
Now, after you have prevented Spotlight from indexing the “Diablo 3” folder, follow the next guide to fix the permissions on the “Diablo 3” and “Battle.net” folders.
As of November 18, 2024 I’m on an M1 iMac running Monterey 12.7.6 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 steps below, make sure that Diablo III and Battle.net applications are NOT running.
1.) While the Finder is active, go to Go menu > Applications > Select the “Diablo III” folder
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”, then click the drop down button underneath that has 3 dots in a circle 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”. For example: I have three “Names”: my account name, admin, and everyone. The most important “Name” to do this step on is “everyone”. Make sure you “Apply to enclosed items…” even if “Privilege” is already set to “Read & Write”.
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 step 5 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.
You may not need to follow the next set of instructions, but I’m going to add them anyway to (hopefully) resolve future crashing/lag/slow downs:
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)
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.
4 Likes
I did not expect the permissions and scan recommendations to help at all, since Rosetta seemed to work fine. But I just played for about 45 minutes without any crashes without Rosetta on my M4 Pro machine. Thank you @TheCyclo.
You are very welcome!
I have the same problem Mac Book pro M3 max. An emergency exit! I changed the screen resolution in the game to 2992x1934x60.
It just started to crash to the menu Battle.net.
I don’t know what to do next.
It keeps asking to update. I finish downloading the update, enter the game and it crashes again. And so in a circle! Help!
Hi All — (Mac User with a fully juiced Mac Studio) — This crashing/restarting has been an issue now since late last year after a Wednesday update. Ive tried everything. Repaired, Reinstalled, fixed permissions (as TheCyclo suggested) . Nothing seems to change anything. I might play for 5 min or I might play for 25, but inevitably it crashed when alot of action is going on on-screen. It’s a massive pain for a game we love. You would think Blizzard could back-track and see what happened. Frustrating to say the least.
1 Like
So another update: Im not sure why but Diablo is using a crazy amount of Memory… obviously a little crazy for such an old game… AND this season especially I find it crashing when there is alot going on onscreen… 8 outta 10 times it’s when Gold is raining from the sky in the new Season… COME ON BLIZZARD… WTF?
1 Like
2.8.0 Build Season 36 … Shocker… no change. Still crashes after ive been playing for around 10 minutes and usually when alot is happening on screen. Blizzard PLEASE…especailly with the new MAC OS Update dropping… please look into this.
I can’t believe this would help but it did. I was able to finish a greater rift without a crash on Tahoe.
M2 Max. I was booted from the game briefly today for a “patch update”. After this, I am repeatedly freezing and having to force-shutdown my Mac. I can’t even force quit.
Once was definitely in one of those enmity things. The other…I think so but can’t recall. Which is really scary because I play hardcore characters.
However, these two times, it at least seems to have removed my character upon crashing.
Ugh.
Note: I’m pretty sure this only happened in fullscreen mode. See, I hadn’t played for years. Started up a character yesterday. I started in fullscreen, but switched to windowed so I could send an meail. And then….the game crashed every single time I tried to switch back. So I stayed in windowed, which is fine except for the possibility of accidentally clicking off-screen while the action is on. (For some reason, I ended up back in fullscreen after the ‘patch’).
I’m back in windowed for now. I’ll update this again if I don’t get anymore crashes in windowed.
(And I can’t seem to start a topic. I’ve posted so much around here, then took a several year break. Did they wipe all that when Microsoft bought Blizzard or something?)
Update: was good for ~5h in windowed mode, then regular crashing.
Every time I crashed, the most recent sounds played in a loop. Until the last time. Hardcore char, easily clearing T12, wiped out after a couple of days (sick, so I wasn’t working).
I had backup items so I guess I’ll start another of the same class and level super fast (barbarian). But yeah…I dunno. I guess I can’t play hardcore anymore. Getting killed by crashes because Microsoft bought Blizz and doesn’t particularly care about OSX is unpleasant.
But that’d mean seasonal normal and..ugh… I just built up from nothing.
Suppose I can burn through my non-seasonal hardcore chars next, one crash after the other. Then stick to seasonal normal if/when I play, since I doubt this will be fixed ever.
Enmity things seem to be the biggest culprit. Lots going on the screen
Update: brought another barb up to T8 melting. Freeze. The currently playing sounds looped for a few seconds. It quit. It said “updating patch”. That quickly went away and it said “updated”. I logged back in…. my video settings were reset to the minimum resolution and fullscreen.
Went back to max. Am in windowed mode. It seems clear that this character is going to get wiped out in another crash.
If I feel like playing after that happens, I suppose I’ll either (1) play an alt. game where I see how far I can get before Microsoft crash-kills me, or (2) play only non-hardcore seasonals, or (3) do something else.
Annoying as hell.
Yup. Crash-killed the second char. Guess hardcore (or Mac more generally) is simply not playable.
I’ll try the Cyclo thing.
I also appended: going to system settings –> privacy and security –> accessibility, and let Diablo III control computer (this had been turned off at some point).
I suppose I still have a nearly last-gen intel imac. Maybe I just have to play on that. Ugh.
Edit:
Yeah. Cyclo’s stuff didn’t help one bit. It’s either lack of support or worse. D3 is just gonna crash every 15-45 minutes, and hardcore characters are a dumb thing to play.
Great ad for mac users considering running windows via one of the alternatives…
EDIT: LOL…crashed out on my level 10 normal seasonal. Definitely no more hardcore. Shame. Kept me on my toes.