lol - you must have stock in apple and amd…the solution to this is not to tell people go buy a 1-2k high end graphics card. many of use had absolutely NO problems like this till 8.3. Add to that I’ve done the boot camp /win10 and tested - while not the exact same issues (well still screen freezes occasionally). no matter what graphics setting I used under windows (tested DX12 down to DX11 legacy, all resolutions available, etc) lag builds over about 30 minutes to the point I can move, and then the game locks, so that I have to pop up task manager and kill the WoW process.
This is ABSOLUTELY something in the way they are trying to directly address the intel gpu chipset…
1 Like
In this case, the problem is…finding the problem. They thought they had it right when they released 8.3. Nope. So they tried to resolve that with the last patch released yesterday. That not only didn’t fix it, it made it worse. Yikes.
So now the issue is finding what change caused this bug to trigger, hopefully for real this time. They likely released yesterday’s patch as an “it’s better to give them something that might work than nothing at all” from the wording they used regarding that patch. That backfired big time. As a result I suspect they’re being a bit more meticulous with the next attempt so it has the best chance of succeeding. And since there’s no blue post updating us on the situation, I would surmise they’re waiting until they have something more concrete this time before they either say anything or release a (hopefully) real fix for the issues in this thread.
Keep in mind that as I noted above, even if they found the exact cause today, they’d need to make a new internal build and test it thoroughly before releasing it or perhaps even telling us about it. Then they have to push the commit to the CDN. They already got bit in the derriére with this last patch. I doubt they want to repeat that mistake. I certainly wouldn’t want to.
Barring a super late night crunch session that yields positive results, I wouldn’t expect anything to be said until at least tomorrow. I guess we’ll find out when we find out. I’d love to stick around and keep watch tonight, but I’ve been up for nearly 36 hours now and am about to take a Unisom so I can get some sleep. I’ll keep my fingers crossed that they come up with something before I wake up tomorrow. 
3 Likes
Thank you for the your insightful replies. Very helpful to cut through the noise and (rightfully deserved/justified) complaining. Sleep well!
Ok, while all that is likely true, one simple thing would make this situation far less toxic: a blue just communicating with us as the process goes. Give us an update once a day at least. This is just piss poor community service, regardless of the bug in question.
2 Likes
Would you please quit being a wow apologist and read any of numerous accounts of people clearly saying this was an issue on the PTR and it was reported then. Quit with your BS. They KNEW this was going to crash macs and they went head with the release anyways, because…? Yeah, because they don’t give a rip. This was not some surprise that suddenly showed up on patch day. They screwed us and put us behind because they couldn’t admit they weren’t ready and delay the release. That’s why I unsub’d. My Conjurer is up to lvl 20 now. Lol wanna bet I hit cap before Mac users can play wow?
12 Likes
Mostly reporting the same problems as everyone else. With the Uldum assault I’ve also noticed the last boss encounter completely cripples my fps. Is anyone else having that issue on macs or possibly an unrelated issue?
My freezes and crashes tend to happen when multiple effects go off at once, which makes BG’s a particular hotspot for freezes to me. I’m currently not playing after I notice freezing as it tends to indicate imminent total system freeze, forcing me to hard reset the laptop by holding down the power, which I believe could be damaging to my system?
If I’m being overly concerned about damage to my hardware I’d appreciate if someone let me know, as I’m not super savvy with pc maintenance.
This happened to macs back in WoD. After 2 months they gave like 5 days free so I wouldnt expect much. We have 2 brand new macbook pros 13 or 15s not sure and they are crashing and freezing pretty often. When they dont freeze the fps is pretty stuttery. Zero issues until 8.3 dropped.
2 Likes
I’ve posted twice before in this thread. Specs:
MacBook Pro (13-inch, Late 2016, Four Thunderbolt 3 Ports)
2.9 GHz Intel Core i5
8 GB 2133 MHz LPDDR3
Intel Iris Graphics 550 1536 MB
I logged in after the most recent update with high hopes. As soon as I took my level 71 warlock into a dungeon, I got the spinning color wheel of death. My computer completely froze and I had to do a hard restart.
Like so many others in this thread, I am discouraged and frustrated, and I feel both cheated and disrespected. Until 8.3, I felt like Blizzard cared about my gameplay experience and valued me as a customer. Now, I’m not sure I’ll ever again feel wholly comfortable playing the game, knowing that with any new update, Mac users might potentially run into a serious error that is not competently and respectfully addressed by the administration of the game.
5 Likes
Yup. Agreed. Already happened to me once in WoD. Unfortunately unlike WoD I’ve already bought the next xpac. I wont be pre purchasing again.
LOL. I didn’t say anyone needs to go buy a high end 1-2k graphics card. What I did say was that if you want a better gaming experience overall, you should consider an dGPU vs iGPU. That could mean your next machine that you purchase in the future OR that could mean get an eGPU if you have a TB3 machine.
That comment had nothing to do with buying a video card to fix the issue, the intel issue will get fixed at some point, but even when it gets fixed you will still be playing at a graphic settings of 1-3 on average, vs 6-9 on average with an dGPU/eGPU.
1 Like
…and then there’s this… hard to kill a world boss with this crap persisting for 9 days now… name 10 things more fun than WoW on a Mac in 8.3? Having my fingernails ripped out comes to mind…
panic(cpu 1 caller 0xffffff7f9d03fad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since wake (35760 seconds ago): 3577, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since wake (35760 seconds ago): 3565, last successful checkin: 120 seconds ago
Backtrace (CPU 1), Frame : Return Address
0xffffff914079b820 : 0xffffff801bf3bb1b
0xffffff914079b870 : 0xffffff801c0733e5
0xffffff914079b8b0 : 0xffffff801c064e5e
0xffffff914079b900 : 0xffffff801bee2a40
0xffffff914079b920 : 0xffffff801bf3b207
0xffffff914079ba20 : 0xffffff801bf3b5eb
0xffffff914079ba70 : 0xffffff801c6d2575
0xffffff914079bae0 : 0xffffff7f9d03fad5
0xffffff914079baf0 : 0xffffff7f9d03f7e6
0xffffff914079bb10 : 0xffffff801c666fcb
0xffffff914079bb60 : 0xffffff801c670083
0xffffff914079bca0 : 0xffffff801c022c22
0xffffff914079bdb0 : 0xffffff801bf41998
0xffffff914079be10 : 0xffffff801bf18625
0xffffff914079be70 : 0xffffff801bf2f0d5
0xffffff914079bf00 : 0xffffff801c04b485
0xffffff914079bfa0 : 0xffffff801bee3226
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[EFAA17B9-A62C-30B7-9602-0BB5282EDDD6]@0xffffff7f9d03e000->0xffffff7f9d046fff
BSD process name corresponding to current thread: watchdogd
Mac OS version:
19C57
Kernel version:
Darwin Kernel Version 19.2.0: Sat Nov 9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64
Kernel UUID: C3E7E405-C692-356B-88D3-C30041FD1E72
Kernel slide: 0x000000001bc00000
Kernel text base: 0xffffff801be00000
__HIB text base: 0xffffff801bd00000
System model name: iMac16,2 (Mac-FFE5EF870D7BA81A)
System shutdown begun: NO
Panic diags file available: YES (0x0)
System uptime in nanoseconds: 54882117805742
last loaded kext at 41680751486: >!ATopCaseHIDEventDriver 3420.1 (addr 0xffffff7f9f2de000, size 61440)
last unloaded kext at 54757269927103: >usb.!UHostPacketFilter 1.0 (addr 0xffffff7f9d53d000, size 24576)
loaded kexts:
!ATopCaseHIDEventDriver 3420.1
@fileutil 20.036.15
AudioAUUC 1.70
AGPM 111.4.1
!APlatformEnabler 2.7.0d0
X86PlatformShim 1.0.0
@filesystems.autofs 3.0
!AUpstreamUserClient 3.6.8
!AHDA 283.15
!AGraphicsDevicePolicy 4.5.21
@AGDCPluginDisplayMetrics 4.5.21
!A!IBDWGraphics 14.0.3
!AHV 1
|IOUserEthernet 1.0.1
|IO!BSerialManager 7.0.2f4
pmtelemetry 1
@Dont_Steal_Mac_OS_X 7.0.0
|Broadcom!B20703USBTransport 7.0.2f4
!A!IBDWGraphicsFramebuffer 14.0.3
eficheck 1
!AThunderboltIP 3.1.3
!ASMCLMU 212
!ALPC 3.1
!AMCCSControl 1.13
!A!ISlowAdaptiveClocking 4.0.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
|!ABCM5701Ethernet 10.3.5
AirPort.BrcmNIC 1400.1.1
!AAHCIPort 341.0.2
@filesystems.apfs 1412.61.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 3420.2
!AInputDeviceSupport 3420.4
!AHS!BDriver 3420.1
IO!BHIDDriver 7.0.2f4
!AHIDKeyboard 209
@kext.triggers 1.0
DspFuncLib 283.15
@kext.OSvKernDSPLib 529
!AGraphicsControl 4.5.21
|IOAVB!F 800.17
!ASSE 1.0
@!AGPUWrangler 4.5.21
|Broadcom!BHost!CUSBTransport 7.0.2f4
|IO!BHost!CUSBTransport 7.0.2f4
|IO!BHost!CTransport 7.0.2f4
|IO!B!F 7.0.2f4
|IO!BPacketLogger 7.0.2f4
!AHDA!C 283.15
|IOHDA!F 283.15
@!AGraphicsDeviceControl 4.5.21
|IOAccelerator!F2 438.2.8
|IONDRVSupport 569.3
!AThunderboltEDMSink 4.2.2
!ASMBus!C 1.0.18d1
|IOGraphics!F 569.3
|IOSlowAdaptiveClocking!F 1.0.0
!ASMBusPCI 1.0.14d1
X86PlatformPlugin 1.0.0
IOPlatformPlugin!F 6.0.0d8
@plugin.IOgPTPPlugin 800.14
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.40.3
|IOEthernetAVB!C 1.1.0
|IO80211!F 1200.12.2b1
mDNSOffloadUserClient 1.0.1b8
corecapture 1.0.4
|IOSkywalk!F 1
|IOAHCI!F 290.0.1
usb.!UXHCIPCI 1.2
usb.!UXHCI 1.2
!AThunderboltDPOutAdapter 6.2.4
!AThunderboltDPInAdapter 6.2.4
!AThunderboltDPAdapter!F 6.2.4
!AThunderboltPCIDownAdapter 2.5.2
!AThunderboltNHI 5.8.1
|IOThunderbolt!F 7.4.7
|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.60.3
|IOSCSIBlockCommandsDevice 422.0.2
!ACredentialManager 1.0
KernelRelayHost 1
!ASEPManager 1.0.1
IOSlaveProcessor 1
|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
|IOTimeSync!F 800.14
|IONetworking!F 3.4
|IOReport!F 47
!AACPIPlatform 6.1
!ASMC 3.1.9
watchdog 1
|IOPCI!F 2.9
|IOACPI!F 1.4
@kec.pthread 1
@kec.corecrypto 1.0
@kec.Libm 1
If they are 15" or 16" turn off graphic switching, so it forces it to use the AMD card, and they probably won’t crash anymore. If they are 13" then they have an intel graphics card, so they will probably crash.
I’m looking forward to actually trying the raid in six months when Blizzard actually fixes the problem. Maybe six months is being too generous…
2 Likes
I play on a MacBook Pro, MacOS Catalina, Version 10.15.2.
-Retina, 13-inch, Early 2015.
-Processor 2.7 GHz Dual-Core Intel Core i5
-Memory 8 GB 1867 MHz DDR3
-Graphics Intel Iris 6100 1536 MB
I have never had ANY issues playing the game until 8.3 was released. Typically in the new zones/N’Zoth invasions points is where I have a majority of my issues. The game either rainbow wheel “stutters” for 20-30 seconds & then loads (has caused deaths), “stutters” & the computer requires a hard manual restart, OR the computer black screens & completely restarts on it’s own.
I only play WoW for the raiding. I have been in a raid guild with the same people for a handful of years & this is completely hindering me from raiding AT ALL. As soon as entering the Ny’alotha raid & we pulled Wrathion my Macbook froze (with the rainbow spinning wheel) & required a manual restart. As soon as I restarted the game did the exact same thing again…HINDERING & CRIPPLING my ability to play the game, hence ending my raid night 20 minutes into entering Ny’alotha.
The “fix” that was pushed on 1/21/20 to “fix” these MacOS problems has done NOTHING. I have been reading the forums & am confident I am NOT the only player experiencing these problems.
I just paid for a 6 month subscription in November and You (Blizzard) should be ashamed for pushing out this UNPLAYABLE patch for MacOS, affecting and hindering a chunk of your player base. I want to be compensated OR reimbursed for the time I am not being able to play the game & doing what I enjoy while playing. I’ve fallen behind on current content thus hurting not only my raid spot but also my guild.
4 Likes
I’ve been trying the Halls of Origination scenario nearly every night since the patch to see if it’ll work. It hasn’t once. Always freezing right when I try to enter the Vault of Lights or whatever the big room with the mobs patrolling is. Stage five. Someone else in this thread already posted my specs.
I’ve been excited about 8.3 since it was announced. I’ve been excited about getting back into the raiding scene. I’ve been excited about the character I boosted with my Shadowlands buy. Now I’m worried I’ll never get to experience anything in this game the way I should be able to.
This really hurts.
3 Likes
Crashes and stutters seem to coincide with AOE attacks both player and NPC.
I’ve noticed, does anyone else see the same pattern.
1 Like
The patch appears not to have worked. I’m still crashing (spinning rainbow ball every time I encounter more than a few mobs). I haven’t been able to do anything of consequence. This will be week two and it’s very frustrating. I’m paying for this. Figure it out, Blizzard. Get your sh*t together.
13 in MacBook Pro
2.3 GHz Quad-Core Intel Core i5
8GB 2133 MHz LPDDR3
Intel Iris Plus Graphics 655 1536 MB
Bug went away for a couple of days, but now seems to be back in full force. Keeping my sub cancelled it seems, oh well!
1 Like
MacBook Pro (15-inch, 2018)
2.2 GHz Intel Core i7
16 GB 2400 MHz DDR4
Radeon Pro 555X 4 GB
Intel UHD Graphics 630 1536 MB
Everything was working fine as of last night my time sydney au
got home today logged in on all my toons can only move a feww feet then Constant Lag not disconnecting though
also Classic works fine with over 400 people in ogrimmar
any help would be appriciated ty
I really hope this gets fixed soon. I miss raiding and m+… not enough room for bootcamp
1 Like