Mac issues - CRASHING, LAGGING AND STUTTERING AFTER 8.3

I completely agree with this! Just tried a normal war front didn’t even get 20 seconds in before a complete crash - just can’t play until this is fixed :frowning:

just to add - i’m also very frustrated not being able to do new content, M+ or raid, nothing i usually do.

1 Like

Since patch release day, I could do most of solo content but nothing else.

The game either crashes or stutters 10-30 seconds before deciding to run again.%99 of the time this is during raids, dungeons or when it’s too crowded in open world.

It just happened again right after I finished 3 world quests and was on my way to turn them in. When I relogged a new assault was on board and everything I worked for was gone. Super cool.

So only boring repetetive daily quests for these last 5 days; can’t raid, can’t dungeon, can’t pvp…giving up.

MacOS Catalina 10.15.1
MacBook Pro (13-inch, 2018)
Processor: 2,3 GHz Quad-Core Intel Core i5
Memory: 8 GB 2133 MHz LPDDR3
Graphics: Intel Iris Plus Graphics 655 1536 MB

2 Likes

it is really hard to do the quests or the daily limited things in the new patch
today it crashed during doing N’Zoth Assaults… all my sanity is lost when i returned so one day is lost thank you blizzard…
do i get a one day extra game time? is there any compensation for players struggling on mac in these days? no… interesting…

3 Likes

I truly hate to say this as I hate to point fingers and understand the magnitude of software development - but OMG did you F.U. badly this time. The “Fix” has made things even worse so it seems. Aren’t you guys running MAC’s to test this?

Here we go (again) … And yes I agree with all statements that for ONCE Blizzard should do something to COMPENSATE us.

EDIT: I already send in the requested spx file by a ticket. So removing all error details here.

EDIT2: Ticket reply : Suggesting to update to iOS 10.15.3 ? For real, this is a BETA2 stage update that is not applied automatically by apple. Can someone explain why you want us to update to a BETA and hope you do realize we are running other software that might be influenced by this request…

EDIT 3: providing my MAC stats for the community:
MacBook Pro (Retina, 15-inch, Mid 2015)
2,5 GHz Quad-Core Intel Core i7
16 GB 1600 MHz DDR3
AMD Radeon R9 M370X 2 GB
Intel Iris Pro 1536 MB

5 Likes

Do any Blizzard staff even read this topic?!

1 Like

If that can help someone, I made a huge breakthrough.
Couldn’t get past the step 7 of Halls these lasts days. Actually tried a lot of things with graphics but maybe not the right combinations.

Saw on US forum a guy that had freezes during assault tried this
All graphics to 1
texture resolution: low
texture filtering: bilinear
projected textures: disabled

Then during the assault, i kept the camera away from the beams of light, which clearly (like all azerite based graphics spells I have found out with crashes experiences those last few days) are causing the troubles.
Try padpedaling to not face the huge streams of light that are created by the puzzle, maintain camera to the floor by locking it with mouse right click kept on, and deal with the boss.
Like me, you should get 4-5 huge freezes but it will eventually stop and let you dps the boss. After that (for the scenario part - cause the rest i haven’t tested), you will be able to complete scenario

hope this helps

I have the same settings as @Gombaa and it also happens to me. I am extremely pissed because I bought subscription because of the new patch. I could not wait for it and it is completely unplayable! I am requesting a refund. The only thing I do, is forcing my computer to restart all the time! It takes so long to fix it!

2 Likes

Hey blizzard ? I seriously hope you are plaining to fix this problem in a couple of hours.
You clearly failed. Do anything you can to satisfy your customers…

2 Likes

So i just tested a thing. I went on my DH and nuked the four training dummies for like four+ minutes, no freeze. Went back on my rogue to farm some transmog, in combat with trash/bosses I instantly get freezes again. What could this mean?

Having the same problems on my Macbook Pro (touchbar). Only when I try to play the new content, no issues when I level alts

1 Like

Having the same issues on my MacBook Pro 2015. Not been able to complete the Halls of Origination scenario at all and at first I thought it may be a problem with my Mac so wiped it and reinstalled everything and still getting the same issues at Stage 6 of the scenario. I was able to complete the Worgen heritage armour questline absolutely fine so for me it seems like it’s just a problem with the scenario. Really annoying that I’m not able to enjoy the rest of the content of the patch :unamused:

1 Like

Yup.
Very same Problems for me here aswell. Been Playing WoW for years now on this and past MacBook Pros and it has always been a pleasure, even on close to highest Graphic/sound settings. ever since 8.3 dropped, so did the game. All the way up to the Mac completely crashing. Help us Blizz :sunny:

    panic(cpu 0 caller 0xffffff7f90abd232): "Graphics firmware encountered an exception (eip: 0xf475, fault #: 0xd)\n"@skl/sched3/IGGuC.cpp:864
Backtrace (CPU 0), Frame : Return Address
0xffffff8122683b70 : 0xffffff800db3bb1b 
0xffffff8122683bc0 : 0xffffff800dc733e5 
0xffffff8122683c00 : 0xffffff800dc64e5e 
0xffffff8122683c50 : 0xffffff800dae2a40 
0xffffff8122683c70 : 0xffffff800db3b207 
0xffffff8122683d70 : 0xffffff800db3b5eb 
0xffffff8122683dc0 : 0xffffff800e2d24f9 
0xffffff8122683e30 : 0xffffff7f90abd232 
0xffffff8122683e80 : 0xffffff7f90a35d24 
0xffffff8122683ee0 : 0xffffff800e240ccd 
0xffffff8122683f30 : 0xffffff800e23f612 
0xffffff8122683f70 : 0xffffff800e23eb9c 
0xffffff8122683fa0 : 0xffffff800dae213e 
      Kernel Extensions in backtrace:
         com.apple.driver.AppleIntelKBLGraphics(14.0.3)[1B1F5C29-179F-374D-BACF-919D3A83FBBD]@0xffffff7f90a34000->0xffffff7f90b26fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[1286D5E5-A6A1-3C44-A244-04C068903DB2]@0xffffff7f8e52f000
            dependency: com.apple.iokit.IOSurface(269.6)[640503DC-6033-3EF6-85F4-F48282EF48DD]@0xffffff7f9092b000
            dependency: com.apple.iokit.IOGraphicsFamily(569.3)[7B5CA52B-0BD1-34AB-BFC9-7D5C3A0DBE7C]@0xffffff7f8eecc000
            dependency: com.apple.iokit.IOAcceleratorFamily2(438.2.8)[9176E894-E24A-36BA-AFDA-0DB11F3F512A]@0xffffff7f9095c000

BSD process name corresponding to current thread: kernel_task
1 Like

Having the exact same issues as stated by others on early 2015 macbook pro. It’s made my whole computer crash twice and doing anything instanced is pretty much impossible.

1 Like

and next, next , next, next, next death game

panic(cpu 2 caller 0xffffff7f922441ec): “Enter debugger: submitToRing: Work queue failure detected”@bdw/IGHardwareRingBuffer.cpp:1486
Backtrace (CPU 2), Frame : Return Address
0xffffff811bf73aa0 : 0xffffff800f33bb1b
0xffffff811bf73af0 : 0xffffff800f4733e5
0xffffff811bf73b30 : 0xffffff800f464e5e
0xffffff811bf73b80 : 0xffffff800f2e2a40
0xffffff811bf73ba0 : 0xffffff800f33b207
0xffffff811bf73ca0 : 0xffffff800f33b5eb
0xffffff811bf73cf0 : 0xffffff800fad24f9
0xffffff811bf73d60 : 0xffffff7f922441ec
0xffffff811bf73d70 : 0xffffff7f922047b4
0xffffff811bf73da0 : 0xffffff7f9220cd79
0xffffff811bf73dd0 : 0xffffff7f9220d214
0xffffff811bf73e10 : 0xffffff7f91d5c966
0xffffff811bf73e60 : 0xffffff7f91d6a438
0xffffff811bf73ea0 : 0xffffff7f91d69bf8
0xffffff811bf73ee0 : 0xffffff800fa40ccd
0xffffff811bf73f30 : 0xffffff800fa3f612
0xffffff811bf73f70 : 0xffffff800fa3eb9c
0xffffff811bf73fa0 : 0xffffff800f2e213e
Kernel Extensions in backtrace:
com.apple.iokit.IOAcceleratorFamily2(438.2.8)[9176E894-E24A-36BA-AFDA-0DB11F3F512A]@0xffffff7f91d58000->0xffffff7f91e1bfff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[2FAEE793-59BC-3ADF-A5E2-3BC8760AFE0B]@0xffffff7f90392000
dependency: com.apple.iokit.IOPCIFamily(2.9)[1286D5E5-A6A1-3C44-A244-04C068903DB2]@0xffffff7f8fd2f000
dependency: com.apple.iokit.IOSurface(269.6)[640503DC-6033-3EF6-85F4-F48282EF48DD]@0xffffff7f907b5000
dependency: com.apple.iokit.IOGraphicsFamily(569.3)[7B5CA52B-0BD1-34AB-BFC9-7D5C3A0DBE7C]@0xffffff7f906cc000
dependency: com.apple.iokit.IOReportFamily(47)[E3C37E96-3AFA-301F-B89C-719FB3D4DA53]@0xffffff7f900c8000
com.apple.driver.AppleIntelBDWGraphics(14.0.3)[576BBE48-1D27-38A2-8DF4-E336156CA95B]@0xffffff7f921d7000->0xffffff7f92270fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[1286D5E5-A6A1-3C44-A244-04C068903DB2]@0xffffff7f8fd2f000
dependency: com.apple.iokit.IOSurface(269.6)[640503DC-6033-3EF6-85F4-F48282EF48DD]@0xffffff7f907b5000
dependency: com.apple.iokit.IOGraphicsFamily(569.3)[7B5CA52B-0BD1-34AB-BFC9-7D5C3A0DBE7C]@0xffffff7f906cc000
dependency: com.apple.iokit.IOAcceleratorFamily2(438.2.8)[9176E894-E24A-36BA-AFDA-0DB11F3F512A]@0xffffff7f91d58000

BSD process name corresponding to current thread: kernel_task

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: 0x000000000f000000
Kernel text base: 0xffffff800f200000
__HIB text base: 0xffffff800f100000
System model name: MacBookAir7,2 (Mac-937CB26E2E02BB01)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 13472661775946
last loaded kext at 11936784651999: >usb.IOUSBHostHIDDevice 1.2 (addr 0xffffff7f92ce0000, size 45056)
last unloaded kext at 12166339811715: >usb.cdc 5.0.0 (addr 0xffffff7f92c50000, size 28672)
loaded kexts:

AudioAUUC 1.70
@fileutil 20.036.15
AGPM 111.4.1
!APlatformEnabler 2.7.0d0
X86PlatformShim 1.0.0
@filesystems.autofs 3.0
!AHDA 283.15
!AUpstreamUserClient 3.6.8
!AGraphicsDevicePolicy 4.5.21
@AGDCPluginDisplayMetrics 4.5.21
!AHV 1
|IOUserEthernet 1.0.1
|IO!BSerialManager 7.0.2f4
pmtelemetry 1
@Dont_Steal_Mac_OS_X 7.0.0
!A!IBDWGraphics 14.0.3
!ACameraInterface 7.6.0
eficheck 1
!ABacklight 180.1
!A!IBDWGraphicsFramebuffer 14.0.3
!A!ISlowAdaptiveClocking 4.0.0
!AMCCSControl 1.13
!AThunderboltIP 3.1.3
!ALPC 3.1
!ASMCLMU 212
!UCardReader 489.60.3
!AVirtIO 1.0
@filesystems.hfs.kext 522.0.9
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
!ATopCaseHIDEventDriver 3420.1
@filesystems.apfs 1412.61.1
!AAHCIPort 341.0.2
AirPort.BrcmNIC 1400.1.1
@private.KextAudit 1.0
!ASmartBatteryManager 161.0.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
usb.!UHostCompositeDevice 1.2
@kext.triggers 1.0
DspFuncLib 283.15
@kext.OSvKernDSPLib 529
!AGraphicsControl 4.5.21
|IOAVB!F 800.17
!ASSE 1.0
!ABacklightExpert 1.1.0
|IONDRVSupport 569.3
@!AGPUWrangler 4.5.21
@!AGraphicsDeviceControl 4.5.21
|IOAccelerator!F2 438.2.8
|IOSlowAdaptiveClocking!F 1.0.0
!ASMBus!C 1.0.18d1
X86PlatformPlugin 1.0.0
IOPlatformPlugin!F 6.0.0d8
!AHDA!C 283.15
|IOGraphics!F 569.3
|IOHDA!F 283.15
@plugin.IOgPTPPlugin 800.14
|IOEthernetAVB!C 1.1.0
|Broadcom!BHost!CUSBTransport 7.0.2f4
|IO!BHost!CUSBTransport 7.0.2f4
|IO!BHost!CTransport 7.0.2f4
usb.!UHub 1.2
usb.networking 5.0.0
|IOAudio!F 300.2
@vecLib.kext 1.2.0
|IOSerial!F 11
|IOSurface 269.6
@filesystems.hfs.encodings.kext 1
!AHS!BDriver 3420.1
IO!BHIDDriver 7.0.2f4
|IO!B!F 7.0.2f4
|IO!BPacketLogger 7.0.2f4
!AMultitouchDriver 3420.2
!AInputDeviceSupport 3420.4
!AHIDKeyboard 209
!AHSSPIHIDDriver 58
|IOAHCIBlock!S 316.40.3
|IOAHCI!F 290.0.1
!AThunderboltDPInAdapter 6.2.4
!AThunderboltDPAdapter!F 6.2.4
!AThunderboltPCIDownAdapter 2.5.2
!AThunderboltNHI 5.8.1
|IOThunderbolt!F 7.4.7
|IO80211!F 1200.12.2b1
mDNSOffloadUserClient 1.0.1b8
corecapture 1.0.4
|IOSkywalk!F 1
!AHSSPISupport 58
!A!ILpssSpi!C 3.0.60
!A!ILpssGspi 3.0.60
!A!ILpssDmac 3.0.60
usb.!UXHCIPCI 1.2
usb.!UXHCI 1.2
|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

I haven’t bothered to log on and try anymore. Im waiting for their official statement that the game is actually playable.

2 Likes

In all honesty, I am about to give up on this and stop playing completely, at least until the issue is fixed (not to mention other issues with the latest patch). 5 days of agony, no solution, no deadlines set, nothing. Just some wooshy washy information (we may have a fix, we have a fix, we don’t know when we are going to to deploy it), that to me suggests you do not have a fix (I might be entirely wrong on this) and are in a sort of damage control mode.

I don’t blame them though, not after all those job cuts and bean counter decisions made upstairs. Cheers.

Just hope we get a timely resolution of these issues and move on. Pardon my frustrations, do not wan’t to offend people.

4 Likes

Nvm i’m just tilted af

2 Likes

In my experience, the freezes seem to be triggered by certain graphics/visual effects. Very striking when I was doing Stormsong WQs yesterday: things were fine until I flew over to the Shrine of Storms area and it started raining, at which point things got really BAD. Had some texture glitches in there in-between the 20 sec lags. And it was fine again when I got out of there.

Same situation in Tanaan Jungle: I was fine fishing by the Arakkoa pool area, but when I flew over to the Bleeding Hollow camp and Hellfire Citadel it was unplayable.

1 Like

Tell us the date of a fix please… It’s getting completely annoying…

2 Likes

I just had a freeze. I was in Ironforge. My entire computer froze.
Imac 2017 with 580 video card.
I managed to end it by pressing option-command-escape, or so it seemed. I did not need to force quit anything.
I noticed in the activity monitor’s GPU history (which I keep visible all the time) that there was a massive spike in GPU activity. I guess some procedure got stuck in a loop.

1 Like