[Mac] Rift crash

  • If you are still crashing after porting in or out of a rift, please post your crash report ID.

    5/20/14 Update: We'd like to gather further Mac system information and logs. Please see Machkhan's update for details.

  • Were you freezing before 2.0.5?
  • Thanks Benhameen.

    The freezing is obviously something different. I was hoping it would be the same problem but your post shows otherwise.

    Unfortunately, since we do not have crash reports for hangs this is even harder to fix than the out of memory problem.

    We will try your steps. If anybody have good steps to reproduce this hang please post them.
  • Just to be clear the freeze is always on a loading screen, right?
  • If it happens in window mode, could you try taking a sample?

    You need to select Diablo in Activity Monitor, click on the gear icon(System diagnostics options), and click on Sample.

    Also, post how much CPU Diablo is using and your OS version.
  • If you play in Windowed(Fullscreen) mode, you should be able to force quit by holding option-cmd-esc. That way, you won't have to reboot.
  • Hey all,

    We'd like to gather additional information from any Mac players who continue experience rift crashes/freezes. This will help our Mac team further research this issue. Follow the instructions below to help us out!

    1. Please post the following system information:
    Obtaining and Posting System Information

    a) Click on the Apple Menu while holding down the Option key and select System Information (10.7 and later).

    B) Copy the information from the following sections and paste them into your post. Please copy in the following order: Hardware Overview, Graphics, and Software. Do not include any serial numbers, hardware UUIDs, or account/login names or information in your post.

    2. If you have recently experienced these specific crashes/freezes, first gather the following files:

    You can email those files to this address: macsupport@blizzard.com

    Use this line for the subject: [forum avatar name] [Rift crash] [12878918249]

    Note: No replies will be sent, as this email is used for only for information gathering.

  • 05/20/2014 02:56 PMPosted by MysticalOS
    05/20/2014 02:15 PMPosted by S4d1k
    If you play in Windowed(Fullscreen) mode, you should be able to force quit by holding option-cmd-esc. That way, you won't have to reboot.

    Any chance, you can make full screen mode not suppress system shortcuts like force quit, or expose?
    Most games in full screen mode can be force quit, even hung, but not D3. it locks out expose and system commands.

    The Windowed(Fullscreen) mode is what you want to use if you want system commands.
  • 05/20/2014 02:49 PMPosted by MysticalOS
    05/20/2014 04:40 AMPosted by ringo
    2014/05/20 15:53:55.000 kernel[0]: process Diablo III[2921] thread 336166 caught burning CPU!; EXC_RESOURCE supressed due to audio playback

    Interesting, so it could be an audio hang. I did recall the user in other thread that said they get crash if they use a TP but if they hit M and port using map, they do not. This indicated to me it could be sound related since graphic related wouldn't matter how you ported, you load same assets, but HOW you port has a different sound.

    Unfortunately even if this is true, only helps you exit rifts avoiding portals, still have to take portal in. However, if it's related to the portal sound. that could help isolate. Assuming that users work around ins valid. I'm just relaying information I remember someone else posting so I personally can't validate.

    We have seen this message as well but never got a hang. So we think this is not related.
  • Hi Mac Community,

    Thanks for the submissions so far, here and to our mailbox. They are being reviewed by the team. We'll pass on any additional updates as they come along.

    If you are experiencing these Mac rift crashes/freezes and would like to contribute, please see our post here.