I am getting the same issue. Fatal error at startup of hots. Report ID: EA6C1321-3F57-4913-80E7-5A9341A64FAA
Apple M1 Macbook Air, 16GB RAM, Ventura 13.4.1
HOTS version 2.55.3.89754
Battle.net version: 2.22.0.14235
1 Like
The game crashes during the authentication screen for me.
FF96D354-6D25-4045-8E21-7493A09EDA02
16" Apple M1 Max
Ventura 13.4.1
1 Like
The fact you’re replying gives me hope.
1 Like
47BBB28C-B195-4E79-A672-567AC25CE598
Same here
1 Like
B45AC986-1911-4A9E-A705-54446FBFAFBE
The crash occurs during the ‘authentication’ screen.
MacBook Pro 16-inch, 2019, 2.6 GHz 6-Core Intel Core i7, Intel UHD Graphics 630 1536 MB, 16 GB 2667 MHz DDR4
Same issue as this thread
3 Likes
Same here, MacBook Pro M1 Max Ventura 13.4.1.
1 Like
same here. I’ve tried to open D3 but was stuck in a blow-up loading screen and need to force restart my imac
1 Like
I too have the same issue. A9C169AD-6B0D-4455-9A5D-8C51956BD9C6
Something related to the BlizzardBrowser.app:
/Applications/Heroes of the Storm/*/BlizzardBrowser.app/Contents/Frameworks/BlizzardBrowser Helper.app/Contents/MacOS/BlizzardBrowser Helper
Crashed Thread: 0 CrGpuMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000058
Exception Codes: 0x0000000000000001, 0x0000000000000058
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [1473]
VM Region Info: 0x58 is not in any region. Bytes before following region: 140723034816424
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
mapped file 7ffca2808000-7ffcb193c000 [241.2M] r-x/r-x SM=COW ...t_id=6be86993
Thread 0 Crashed:: CrGpuMain Dispatch queue: com.apple.main-thread
0 <translation info unavailable> 0x102944620 ???
1 Metal 0x7ff81ee5dcb4 MTLResourceListAddResource + 131
2 libsystem_platform.dylib 0x7ff815308603 _sigtramp + 51
3 AppleMetalOpenGLRenderer 0x10e65a7fc GLDPixelConverter::readPixels(id<MTLDevice>, id<MTLComputeCommandEncoder>, GLGOperationRec const&, id<MTLBuffer>, unsigned long, id<MTLTexture>, MTLRegion) + 806
4 AppleMetalOpenGLRenderer 0x10e66b6ce GLDTextureRec::readTextureDataCore(unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, unsigned long, unsigned long, unsigned long, unsigned long, unsigned long, unsigned long, bool, int, int, GLDPixelModeRec const*, void const*, GLDBufferRec*, bool) + 3382
5 AppleMetalOpenGLRenderer 0x10e686a53 gldReadFramebufferData + 553
6 GLEngine 0x7ffa2d294c8e glReadPixels_Exec + 1114
7 libGL.dylib 0x7ffa2d24d9d4 glReadPixels + 42
Tested on another Mac with an older version of the Battle.net launcher and it also did not work. So its broken in:
Battle.net version 2.21.1.14206
and
Battle.net version 2.22.0.14235
Tested on M1 Ultra and x86 Macs, broken in both.
Diablo 3 also freezes and I’m unable to exit.
Hearthstone works.
5 Likes
79144C9E-6994-4059-BAB0-EA23F8B22507. Same issue with crashing on mac
6BA16418-FADE-4101-ACBB-C5BB602E435E
iMac 24-inch, M1, 2021, Ventura 13.4.1
E98B34B6-B79B-4ADC-9E14-0B967BE21CFC
MacBook Air - M2 Chip 8GB
Ventura 13.4.1
Received ‘An unexpected fatal error occurred’ upon startup. FCEB73B2-828C-486F-B3D2-19C323A34286
macOS Monterey 12.6
iMac 24-inch, M1, 2021
An unexpected fatal error occurred.
B2AC512E-A276-464A-A540-F347E9D2F062
Same issue, Mac mini m2 updated. error code: D1869630-FBC6-4DB0-8791-
89DA7DA9F9E6
Are you still holding out on that hope?
Macbook M1
4C7D930D-EA9E-4CBB-8244-4B18156E04EC
I have the issue as well with an x86 MBP running the latest Monterey. Someone below seems to have poinpointed that to an issue with the battle.net launcher, see : [Mac] Game crashes on startup - #38 by Alos-1720
In case it helps
24529AD3-3498-45ED-80C3-2FB9CC191F95
Error:
3F47CBCC-D061-48E4-A500-D383446AFC2B
Same,
8552FF2A-A8C9-49F6-8E38-37FE2B77916F