Crashing, freezing, and stuttering after 8.3 [Intel GPUs]

So what’s next? Apple cs keeps saying it’s your fault, it’s your games fault, and that nothing in the crash reports shows any issue on the Mac side. So, are we supposed to believe them or believe you? When I talk to them, I get a response right away, not three days later, and not the same crap about lowering our settings. You say a fix is to bootcamp, why is there still a Mac download on your website? Why are you still selling a broken game and making money knowing this crap doesn’t work?

14 Likes

yet another hard crash, in “old” content… 11 days left on my sub, so i guess it’s time to pack up and give away my guild, it was fun wile it lasted, which is basically until Legion, then this poor gaming experience on Macs. Is that when Blizz got bought out?

where: Heroic Stromgarde: the game froze a number of times, then crashed on the last fight

who: my warrior

when: about 10:00pm realm time (cst)


panic(cpu 1 caller 0xffffff7f8e6f0ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since wake (16870 seconds ago): 1688, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since wake (16870 seconds ago): 1676, last successful checkin: 120 seconds ago

Backtrace (CPU 1), Frame : Return Address
0xffffff9130a43820 : 0xffffff800db3bb2b 
0xffffff9130a43870 : 0xffffff800dc734d5 
0xffffff9130a438b0 : 0xffffff800dc64f4e 
0xffffff9130a43900 : 0xffffff800dae2a40 
0xffffff9130a43920 : 0xffffff800db3b217 
0xffffff9130a43a20 : 0xffffff800db3b5fb 
0xffffff9130a43a70 : 0xffffff800e2d2b25 
0xffffff9130a43ae0 : 0xffffff7f8e6f0ad5 
0xffffff9130a43af0 : 0xffffff7f8e6f07e6 
0xffffff9130a43b10 : 0xffffff800e26739b 
0xffffff9130a43b60 : 0xffffff800e270443 
0xffffff9130a43ca0 : 0xffffff800dc22d12 
0xffffff9130a43db0 : 0xffffff800db419d8 
0xffffff9130a43e10 : 0xffffff800db18635 
0xffffff9130a43e70 : 0xffffff800db2f0e5 
0xffffff9130a43f00 : 0xffffff800dc4b575 
0xffffff9130a43fa0 : 0xffffff800dae3226 
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[053A5D15-51D4-3E61-978B-EB435FA4BD0A]@0xffffff7f8e6ef000->0xffffff7f8e6f7fff

BSD process name corresponding to current thread: watchdogd

Mac OS version:
19D76

Kernel version:
Darwin Kernel Version 19.3.0: Thu Jan  9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64
Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE
Kernel slide:     0x000000000d800000
Kernel text base: 0xffffff800da00000
__HIB  text base: 0xffffff800d900000
System model name: iMac16,2 (Mac-FFE5EF870D7BA81A)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 159466977626679
last loaded kext at 15609172726629: >!UTopCaseDriver	3430.1 (addr 0xffffff7f8f772000, size 16384)
last unloaded kext at 159377757523107: >usb.!UHostPacketFilter	1.0 (addr 0xffffff7f8ebdb000, size 24576)
loaded kexts:
>!ATopCaseHIDEventDriver	3430.1
>!AGraphicsDevicePolicy	4.7.2
@AGDCPluginDisplayMetrics	4.7.2
>AudioAUUC	1.70
@fileutil	20.036.15
>!AHV	1
|IOUserEthernet	1.0.1
|IO!BSerialManager	7.0.3f5
>!AUpstreamUserClient	3.6.8
>AGPM	111.4.2
>!APlatformEnabler	2.7.0d0
>X86PlatformShim	1.0.0
>pmtelemetry	1
>!A!IBDWGraphics	14.0.4
@Dont_Steal_Mac_OS_X	7.0.0
>!AHDA	283.15
>eficheck	1
>!AThunderboltIP	3.1.3
|Broadcom!B20703USBTransport	7.0.3f5
|!ABCM5701Ethernet	10.3.5
>!ASMCLMU	212
>!ALPC	3.1
>AirPort.BrcmNIC	1400.1.1
>!A!IBDWGraphicsFramebuffer	14.0.4
>!A!ISlowAdaptiveClocking	4.0.0
>!AMCCSControl	1.13
@filesystems.autofs	3.0
>!AVirtIO	1.0
@filesystems.hfs.kext	522.0.9
@!AFSCompression.!AFSCompressionTypeDataless	1.0.0d1
@BootCache	40
@!AFSCompression.!AFSCompressionTypeZlib	1.0.0
>!ASDXC	1.7.7
>!AAHCIPort	341.0.2
@filesystems.apfs	1412.81.1
@private.KextAudit	1.0
>!ARTC	2.0
>!AACPIButtons	6.1
>!AHPET	1.8
>!ASMBIOS	2.1
>!AACPIEC	6.1
>!AAPIC	1.7
$!AImage4	1
@nke.applicationfirewall	303
$TMSafetyNet	8
@!ASystemPolicy	2.0.0
|EndpointSecurity	1
>!AMultitouchDriver	3430.1
>!AInputDeviceSupport	3430.1
>!AHS!BDriver	3430.1
>IO!BHIDDriver	7.0.3f5
>!AGraphicsControl	4.7.2
|IOAVB!F	800.17
>!ASSE	1.0
>DspFuncLib	283.15
@kext.OSvKernDSPLib	529
@plugin.IOgPTPPlugin	810.1
@!AGPUWrangler	4.7.2
|IONDRVSupport	569.4
>!AHDA!C	283.15
|IOHDA!F	283.15
|Broadcom!BHost!CUSBTransport	7.0.3f5
|IO!BHost!CUSBTransport	7.0.3f5
|IO!BHost!CTransport	7.0.3f5
|IO!B!F	7.0.3f5
|IO!BPacketLogger	7.0.3f5
|IOEthernetAVB!C	1.1.0
>!AHIDKeyboard	209
>!ASMBusPCI	1.0.14d1
|IO80211!F	1200.12.2b1
>mDNSOffloadUserClient	1.0.1b8
>corecapture	1.0.4
|IOSkywalk!F	1
@!AGraphicsDeviceControl	4.7.2
|IOAccelerator!F2	438.3.1
>X86PlatformPlugin	1.0.0
>IOPlatformPlugin!F	6.0.0d8
|IOSlowAdaptiveClocking!F	1.0.0
>!AThunderboltEDMSink	4.2.2
>!ASMBus!C	1.0.18d1
|IOGraphics!F	569.4
@kext.triggers	1.0
>usb.!UHub	1.2
>usb.networking	5.0.0
>usb.!UHostCompositeDevice	1.2
|IOAudio!F	300.2
@vecLib.kext	1.2.0
|IOSerial!F	11
|IOSurface	269.6
@filesystems.hfs.encodings.kext	1
|IOAHCIBlock!S	316.80.1
|IOAHCI!F	290.0.1
>usb.!UXHCIPCI	1.2
>usb.!UXHCI	1.2
>!AThunderboltDPOutAdapter	6.2.5
>!AThunderboltDPInAdapter	6.2.5
>!AThunderboltDPAdapter!F	6.2.5
>!AThunderboltPCIDownAdapter	2.5.4
>!AThunderboltNHI	5.8.6
|IOThunderbolt!F	7.6.0
|IONVMe!F	2.1.0
|IOUSB!F	900.4.2
>!AEFINVRAM	2.1
>!AEFIRuntime	2.1
|IOSMBus!F	1.1
|IOHID!F	2.0.0
$quarantine	4
$sandbox	300.0
@kext.!AMatch	1.0.0d1
>DiskImages	493.0.0
>!AFDEKeyStore	28.30
>!AEffaceable!S	1.0
>!AKeyStore	2
>!UTDM	489.80.2
|IOSCSIBlockCommandsDevice	422.0.2
>!ACredentialManager	1.0
>KernelRelayHost	1
>!ASEPManager	1.0.1
>IOSlaveProcessor	1
|IOTimeSync!F	810.1
|IONetworking!F	3.4
|IOUSBMass!SDriver	157.40.7
|IOSCSIArchitectureModel!F	422.0.2
|IO!S!F	2.1
|IOUSBHost!F	1.2
>!UHostMergeProperties	1.2
>usb.!UCommon	1.0
>!ABusPower!C	1.0
|CoreAnalytics!F	1
>!AMobileFileIntegrity	1.0.5
@kext.CoreTrust	1
|IOReport!F	47
>!AACPIPlatform	6.1
>!ASMC	3.1.9
>watchdog	1
|IOPCI!F	2.9
|IOACPI!F	1.4
@kec.pthread	1
@kec.Libm	1
@kec.corecrypto	1.0

It was one thing getting updates the first week or two after the problem started. It’s another to just say something most people here already posted about Then drop off the face of the earth for a few days. Especially after they -yet again- screw customers over with the terrible w3 reforged release.

Just an update to my current experience since my post a couple weeks ago.

Things seem better on my end. My WoW still freezes for 5-6 seconds but resumes. This seems to only happen at a certain threshold of how much there is going on, on my screen. If I go past that threshold and there’s too much going on the screen (Whether it be pulling lots of mobs, lots of effects like patches on the floor, totems or what not) my wow will actually permanently freeze and I have to force quit it. Which brings me to another positive point is that my WoW no longer crashes, at least not yet. This has been my experience before and during the recent update of Mac Version 10.15.3 (19D76).

Summary:
Positives:
My computer does not crash anymore because of WoW.
Freezes are often only 5-6 seconds long instead of permanent (Seems to happen when I hit a certain threshold of how much stuff is going on my screen) (Still difficult to fully enjoy dungeons, especially with bosses in which patches/totems and stuff pop up. E.g Dazar - King’s Rest frequently and consistently froze my computer and made it crash even at one point)

Negatives:
WoW will freeze permanently if I pass that threshold, without crashing my computer, requiring me to force quit it. (Still cannot raid or pull lots of island mobs)

Thank you!

And I’ve decided that 3 weeks was more than enough time for you to come up with something better than “We still aren’t sure of what the issue is”. That is completely unacceptable. Tonight, I crashed 3 times during a horrific vision and lost a WELL EARNED/ HARD WORKED FOR vessel due to YOUR incompetence. And that’s my last straw.

6 Likes

PROGRESS:

I’ve been playing around with the settings

I have found a minor work around, I just have had a crash (freeze) BUT I just finished an entire dungeon as a tank with heavy pulls with no stutters/ freezes/ crashes.

I got the crash (freeze) after sitting in Boralus for a couple minutes, but it was different. I could still move my mouse but I could not force quit, had to reboot.

The workaround (may not work for everyone):
Exact settings
Graphics quality - 2 (Across the board)
Anti-Aliasing - FXAA High
Vertical sync - disabled
Triple buffering - Enabled
MSAA - None
Multisample Alpha Test - Disabled
Post Process AA - FXAA High
Resample Quality - None
Graphics API - Metal
Physics Interactions - Player Only
HUGE
Graphics Card - Intel Iris
(Make sure you SELECT your card and not use auto select, I don’t know why but it works)

Worked for me so far besides the crash (freeze) in Boralus, maybe give it a try

6 Likes

I have been trying a new trick to do something. I survived the World boss in Uldum by turning my character (120 balance Druid) towards the boss, far away from the boss as I could to be in range. Hit moonfire - turned my screen away from the boss with my character still facing the boss. I could not see what was happening, since my camera angle was pointed away, but I only froze for 20-30 seconds, then continued to moonfire and instant cast with the group. – I cannot go into visions without freezing the whole time. Group questing not really possible. But with the screen away method I have done some world quests. Mostly - I just stay off wow, But trying to keep semi geared… So maybe someday I can attempt to raid with my guildies.
I am keeping tabs here.
Since I am off the raid team, and can’t do any content, even old tmog runs cause me to spin and freeze, with a few hard reboots… I am just gonna wait.

2 Likes

I don’t disagree with y’all I think it’s ridiculous that it’s gone on this long, that they’ve blatantly prioritized other issues ahead of this, that they go so long between updates, and that they’re still putting off blame on intel/mac os. I am in the exact same boat as everyone else, I haven’t been able to play properly in 3 weeks and I don’t have the space to bootcamp my mac. I’m not exactly fond of the idea of paying $15/month to play PTR either. However, my point was just that bashing blizzard and complaining no matter what they say or don’t say isn’t productive or constructive and it does nothing to hold them accountable. For all intents and purposes y’all are hollering into the void.

1 Like

Eureka! That’s it!

** Huge **
Graphics Card-Intel Iris

Thanx a lot.

Still freezing 2-3 times in dungeons (shockingly my groups have never kicked me), indefinitely on World Bosses, and even when I first log into Boralus. I don’t dare try LFR. And for the first time I froze fighting 5 Oracles in Sholazar Basin. My game time expires this morning, and I won’t be renewing as of now. I’ll keep checking in on this forum, and hopefully there’s a fix sooner rather than later. I’ll give it a month, and hopefully it’s fixed by March. We’ll see though. Not really feeling confident given what we’ve seen so far. But I’m still hopeful Blizzard can come through and do what’s right for their customers.

This is more useful than all of the stupidity that the idiots at Blizzard have put out in three weeks. This actually works. It won’t completely stop the beach balls but you can finish an instance.

1 Like

We weren’t given any new information at all. It’s just the same “We’re working on it. Thanks for being patient and continuing to put money in our incompetent pockets.” spiel.

8 Likes

Woohoo got the mouse mount with my 6 month subscription and so far it’s looking like the first month out of my six is unplayable, :clap:t2: Awesome!

9 Likes

Drakuloth, How does Blizzard plan to compensate people for whom this bug has made the game unplayable? Also, is there any sense at HQ that this response rate and timetable is completely unacceptable? Are people’s slack boards blowing up? Emergency meetings of the Mac dev team? Saying that you might actually have to reach out to Intel and/or Apple to fix this does not inspire confidence.

11 Likes

You’re definitely onto something. The first time I tried to change the graphics card from auto detect to Intel, my whole computer crashed as soon as I clicked “Apply”. The second time I was able to successfully change the setting, but got a huge lag spike for a few minutes after hitting “Apply” and thought the computer was going to crash again, but it didn’t. Just did two arenas with no lag but as soon as I tried a battleground and got into a large fight the huge lag spikes came back. Things seem marginally better in the outside world, so thanks! But regardless, Blizzard needs to fix this problem. We shouldn’t have to waste our time tinkering with the settings just to make the game slightly more playable. We’re paying customers!

1 Like

I got mine at the tail end of my subscription so at least I have that lol

Maybe in 6 months I’ll have a working game to get the next one

Maybe… probably not though

This is what happens when a company goes the corporate route. They lose there soul and integrity, and I imagine it will only get worse.

7 Likes

Nah, it’s specifically that they went public with their stock, and are now directly beholden to shareholders. Fiduciary duty is a powerful thing and one that almost always results in driving short-term profits over long-term investments (like, say, making sure mac players can actually play.)

1 Like

Not true. Them seeing us angry will scare them (if they are sensible) that unhappy customers leads to loss of business. In fact, I think this thread is worthwhile, because having happy customers is vital for business success. This thread clearly shows we are unhappy.

2 Likes

unhappy customers is only vital if that percentage of players that are truly unhappy is large enough to effect your margins. Truth be told, they can probably save money by understaffing QC and tech support for mac users, and still offset the losses they will make in subs since we’re a minority. And in turn, they can put those salaries into chinese phone games and make much more than if they had put those people on wow for mac error fixing lol.

Adding more to this, if indeed is correct in saying that the average software engineer at blizzard makes 96k/yr, that would require about 6000 people to unsubscribe this year due to unplayable macs to make that persons job worth it if they were putting him towards bug fixing. I’m also guessing that bugs like this are going to take a team to fix, so notch that up a few times and you can pretty easily guess why they dont have any prio on fixing the game for mac users.

3 Likes