Just wait for the new Imac line up machine if u wanna play on a MAC… there is a good chance that we will get something good in First Half of 2020
New IMAC design/graphic with a 30 inches screen. The screen might come with a 6k screen resolution.
Still freezes, hangs, stutters - no more reboot though. Not a fix in my eyes, not even temporarily. Compensation? one month of paid subscription unuseable.
Mind want to share something about that?
1 Like
The Battle Net launcher has crashed my iMac now!!!
Sleep Wake failure in EFI
Failure code:: 0xffffffff 0x0000001f
Please IGNORE the below stackshot
================================================================
Date/Time: 2020-02-06 14:13:10 +0000
OS Version: ??? ??? (Build ???)
Architecture: x86_64
Report Version: 29
Data Source: Stackshots
Shared Cache: 0x3ccc000 DA9591EF-4D0E-3320-A67D-A570D75C925E
Event: Sleep Wake Failure
Duration: 0.00s
Steps: 1
Time Awake Since Boot: 16s
Process: swd [297]
Architecture: x86_64
Footprint: 372 KB
Start time: 2020-02-06 14:13:10 +0000
End time: 2020-02-06 14:13:10 +0000
Num samples: 1 (1)
Thread 0x74b 1 sample (1) priority 4 (base 4)
<thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2>
1 start + 1 (libdyld.dylib + 108541) [0x7fff66d987fd] 1
1 ??? [0x10afdb454] 1
1 ??? [0x10afdb1dd] 1
1 __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 136138) [0x7fff66ef93ca] 1
*1 ??? [0xffffff80002e3206] 1
*1 ??? [0xffffff800099b08a] 1
*1 ??? [0xffffff80008b3f91] 1
*1 ??? [0xffffff800030646a] (running) 1
Binary Images:
0x7fff66d7e000 - 0x7fff66db3fff libdyld.dylib (733.8) <8B0DFE8A-42CF-32C8-B121-83C22BF25F69> /usr/lib/system/libdyld.dylib
0x7fff66ed8000 - 0x7fff66f04fff libsystem_kernel.dylib (6153.81.5) <23909F45-79C3-34C9-A28F-337915925E5E> /usr/lib/system/libsystem_kernel.dylib
Model: iMac16,2, BootROM 232.0.0.0.0, 4 processors, Quad-Core Intel Core i5, 3.1 GHz, 8 GB, SMC 2.32f21
Graphics: kHW_IntelIrisPro6200Item, Intel Iris Pro Graphics 6200, spdisplays_builtin
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1867 MHz, 0x80AD, 0x483943434E4E4E424C54424C41522D4E5544
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1867 MHz, 0x80AD, 0x483943434E4E4E424C54424C41522D4E5544
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x156), Broadcom BCM43xx 1.0 (7.77.106.3 AirPortDriverBrcmNIC-1440.1)
Bluetooth: Version 7.0.3f5, 3 services, 27 devices, 1 incoming serial ports
Network Service: iPhone 2, Ethernet, en7
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: APPLE HDD HTS541010A9E662, 1 TB
USB Device: USB 3.0 Bus
USB Device: TOURO Mobile
USB Device: Bluetooth USB Host Controller
USB Device: FaceTime HD Camera (Built-in)
USB Device: iPhone
Thunderbolt Bus: iMac, Apple Inc., 27.4
Do you think that this was Blizzard’s way of getting the Horde and Alliance to work together and fight a common enemy?
There is a blue post confirming the issue is caused by a bug in the Intel drivers.
Can’t Blizzard revert to the Metal API calls or graphics subroutines/whatever were present in the game in 8.2.5? That was bug free, and neither Apple nor Intel updated their drivers in the meantime.
That would be the first thing to try but if they don’t provide it as solution it means it’s either not easy to accomplish so quickly or for some reason not working.
Also note that 8.3 doesn’t show the issue on older macOS versions: I had the problem on a 13" MacBook Pro with Catalina and by running the game from High Sierra I could play with zero issues and no graphical settings downgrades needed.
I’m playing on Mojave 10.14.6. on an iMac with Iris Pro 6200 graphics, but I had the crashing problem. Now, I can selectively disable particles when I suspect there may be an issue, which is a workaround, but a sucky one.
I’m concerned that if we really are waiting for a fix from Intel/Apple that may take months, and also may not be supplied for 10.14.x. (I have good, albeit boring, reasons for not wanting to upgrade to Catalina)
The game is playable now. But the cost might be high - tortollan calligraphy quests are just invisible.
Even further - last night went to Atal’Dazar and guess what - priest boss blood pools were invisible. And of course the whole battle took a lot longer.
In no way these are driver issues - things used to work just fine before 8.3, so Blizzard sit on your greedy a55es and just fix it properly.
Now that there’s a blue post pointing at Apple and Intel I would like to add that in a preemptive multitasking operating system like windows, macos or linux, an application should not be able to crash the computer. The OS should always stay in control.
If your mac is crashing it is probably due to a fault in macos.
Mine (580 imac) sometimes quits WoW and requires me to log in again without actually resetting the computer, really strange behaviour.
1 Like
(From the US forum - https://us.forums.blizzard.com/en/wow/t/crashing-freezing-and-stuttering-after-83-intel-gpus/411134/1854)
Drakuloth
Hey folks,
The particle density situation is a work around. We’ve confirmed that this appears to be a driver level bug, which means that we cannot fix it and need someone else to do so, as we don’t create drivers for your graphics cards. We’re telling the GPU to do something it’s supposed to be able to do, but due to a bug with the driver’s coding, your machine is getting into a bad state. We added new particle effects with 8.3, but it’s not the core cause, just the trigger for the driver bug.
Being able to disable particle density is a work around that we put in until updated drivers/a new mac OS build are released which fix the problem so that you all can at least play. We’ve already reported the issue to intel. At this time if you are having this problem, you should disable particle density by following the steps that are recommended here. If we hear that a build of mac OS has been resolved which fixes the issue, we’ll let you know.
Another Bullsh*t answer!
I am not USING an intel GPU and I have the same issues, and so are Windows users that experience the same issues!
As reported many times before I am Using an AMD Radeon R9 M370X 2 GB
Their dirvers arent updated, the only thing that IS updated is your game.
This is so obviously YOUR WAY to get around the compensation issues Blizzard are facing.
How about all the other posts:
The lists goes on…
I was already utterly disappointed in the way you address our issues and tickets and things are even declining further which i would not have held for possible.
2 Likes
SIGH now the client hangs as well…
Date/Time: 2020-02-08 10:22:45 +0100
End time: 2020-02-08 10:23:04 +0100
OS Version: Mac OS X 10.15.3 (Build 19D76)
Architecture: x86_64h
Report Version: 29
Data Source: Stackshots
Shared Cache: 0x7374000 430CDBE0-78FD-387A-B4BC-D807C59819C4
Command: Battle.net
Path: /Applications/Battle.net.app/Contents/MacOS/Battle.net
Identifier: net.battle.app
Version: 1.19.1.11809 (1.19.1 (11809))
Parent: launchd [1]
PID: 32433
Event: hang
Duration: 19.73s
Duration Sampled: 4.99s (process was unresponsive for 15 seconds before sampling)
Steps: 50 (100ms sampling interval)
Hardware model: MacBookPro11,5
Active cpus: 8
Time Awake Since Boot: 43000s
Time Since Wake: 4300s
Fan speed: 2209 rpm
Incidentally I’ll add that you can re-enable particle effects for old world- (and a lot of solo) content usually without problems. At least then you’ll be able to do those Tortollan dailies. You obviously WILL continue to experience freezes and crashes in group content, scenarios, and anything graphically intensive introduced in 8.3 if you do this.
And I still don’t buy the explanation that this is a problem requiring a driver fix from Intel. Sorry.
It’s actually a pretty clear-cut driver issue since it’s not only the WoW client freezing or crashing: it’s the whole operating system.
There is no excuse for an operating system to crash or freeze: user applications, no matter how buggy, should simply have no means to cause such problems.
Then why was this problem not present in 8.2.5?
Then why is the problem not present in 8.3 too on exactly the same machine but running High Sierra instead of Catalina?
I don’t doubt 8.3 might have introduced changes triggering the bug, but the bug is ultimately clearly a faulty driver issue.
Why they didn’t revert to 8.2.5 rendering as workaround instead of disabling particle effects entirely I don’t know, but I guess it’s something just not that easy to accomplish in a hotfix.
Any update when our Mac clients won’t freeze anymore??
My point is that the driver bug, if that’s what it is, was also present in 8.2.5 as there have been no changes to the OS in that time. And the freezing issue wasn’t manifest then. (I’m also on a High Sierra system, incidentally).
If you are on High Sierra you should have zero issues playing with particle effects enabled.
As stated, it’s perfectly possible for changes in 8.3 to have uncovered a previously unnoticed bug in the driver, but the bug is still in the driver.
There should be no possible command which an applications can impart to a graphic driver able to cause the system to freeze or crash.
how about gaming ? still freezing and crashing? any fixes?