macbook pro (13-inch, 2017, four thunderbolt)
3.5 GHz Intel Core i7
16 GB 2133 MHz
intel iris plus graphics 650 1536 MB
MacBook Pro 15-inch 2018
2.2 GHz Intel Core i7
32 GB 2400 MHz DDR4
Radeon Pro 555X 4096 MB
Intel UHD Graphics 630 1536 MB
MacOS Mojave 10.14.3 (18D109)
Hardware Overview:
Model Name: iMac
Model Identifier: iMac12,1
Processor Name: Intel Core i7
Processor Speed: 2.8 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 20 GB
Boot ROM Version: 82.0.0.0.0
SMC Version (system): 1.71f22
AMD Radeon HD 6770M 512 MB
Software: macOS High Sierra 10.13.6 (17G5019)
Launching windowed did not produce anything differently.
Hardware Overview:
Model Name: iMac
Model Identifier: iMac12,1
Processor Name: Intel Core i7
Processor Speed: 2.8 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 20 GB
Boot ROM Version: 82.0.0.0.0
SMC Version (system): 1.71f22
AMD Radeon HD 6770M 512 MB
Software: macOS High Sierra 10.13.6 (17G5019)
Trying in window mode - no difference.
My Mac specs:
MacBook Air (13-inch, Early 2014)
Processor 1,7 GHz Intel Core i7
Memory 8 GB 1600 MHz DDR3
Graphics Intel HD Graphics 5000 1536 MB
System MacOS Mojave 10.14.3
I also love the explanation - well we’re working on it but it works on our computers. Should’ve added “Have you tried turning it off and on again”
1 Like
macOS mojave version 10.14.3
MacBook Pro retina 15inch late 2013
processor: 2.3ghz intel corei7
memory 16gb 1600mhz ddr3
graphics intel iris pro 1536 mb
| Model Name: | iMac |
|---|---|
| Model Identifier: | iMac18,3 |
| Processor Name: | Intel Core i5 |
| Processor Speed: | 3.8 GHz |
| Number of Processors: | 1 |
| Total Number of Cores: | 4 |
| L2 Cache (per Core): | 256 KB |
| L3 Cache: | 6 MB |
| Memory: | 40 GB |
| Boot ROM Version: | 166.0.0.0.0 |
| SMC Version (system): | 2.41f1 |
This did not work, game still crashes.
All machine specs and collected files sent by email.
Like, how long do you think this will last? Has there been any similar case? Its getting ridiculous ![:frowning:](https://d3rakab8gpdsa3.cloudfront.net/en/heroes/images/emoji/twitter/frowning.png?v=6" ":frowning:")
Windowed mode was unsuccessful
Specs:
MacBook Pro (15-inch, 2016)
Mojave 10.14.3 (18D109)
2.7 GHz Intel Core i7
16 GB 2133 MHz LPDDR3
Intel HD Graphics 530 1536 MB
Still crashes, seemingly in the same way. My machine:
iMac (Retina 5K, 27-inch, 2017)
macOS High Sierra 10.13.6
Processor: 3.8 GHz Intel Core i5
Memory: 40 GB 2400 MHz DDR4
Graphics: Radeon Pro 580 8192 MB
Process: Heroes [6113]
Path: /Applications/Heroes of the Storm/*/Heroes.app/Contents/MacOS/Heroes
Identifier: com.blizzard.heroesofthestorm
Version: 2.43 [72191] (72191)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Heroes [6113]
User ID: 501
Date/Time: 2019-02-14 18:50:24.022 -0600
OS Version: Mac OS X 10.13.6 (17G5019)
Report Version: 12
Anonymous UUID: F9982FE4-200A-6808-463B-7849CF13C7E8
Time Awake Since Boot: 160000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: _LSContextInitClient queue
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
__cxa_guard_acquire detected deadlock
abort() called
Thread 0 Crashed:: Dispatch queue: _LSContextInitClient queue
0 libsystem_kernel.dylib 0x00007fff7a419b66 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff7a5e4080 pthread_kill + 333
2 libsystem_c.dylib 0x00007fff7a3751ae abort + 127
3 libc++abi.dylib 0x00007fff7826ff8f abort_message + 245
4 libc++abi.dylib 0x00007fff7828b690 __cxa_guard_acquire + 221
5 com.blizzard.heroesofthestorm 0x0000000100da9623 0x100000000 + 14325283
6 com.blizzard.heroesofthestorm 0x0000000100db3db5 0x100000000 + 14368181
7 com.blizzard.heroesofthestorm 0x0000000100dbe7e4 0x100000000 + 14411748
8 com.blizzard.heroesofthestorm 0x00000001027edf5e operator new(unsigned long) + 14
9 com.apple.LaunchServices 0x00007fff538e5f9f invocation function for block in _LSGetSessions() + 122
10 libdispatch.dylib 0x00007fff7a28fdb8 _dispatch_client_callout + 8
11 libdispatch.dylib 0x00007fff7a28fd6b dispatch_once_f + 41
12 com.apple.LaunchServices 0x00007fff5381fa70 _LSGetSession(unsigned int) + 120
13 com.apple.LaunchServices 0x00007fff5381f9cb _LSCopyLocalDatabase + 31
14 com.apple.LaunchServices 0x00007fff538e6c8f invocation function for block in _LSContextInitClient(LSContext*) + 60
15 libdispatch.dylib 0x00007fff7a28fdb8 _dispatch_client_callout + 8
16 libdispatch.dylib 0x00007fff7a2a31e1 _dispatch_queue_barrier_sync_invoke_and_complete + 60
17 com.apple.LaunchServices 0x00007fff538e4e33 _LSContextInitClient(LSContext*) + 209
18 com.apple.LaunchServices 0x00007fff5381f89e _LSContextInit + 182
19 com.apple.LaunchServices 0x00007fff53873d6f _LSCreateDeviceTypeIdentifierWithModelCodeInternal(__CFString const*, unsigned char const*, unsigned char) + 39
20 com.apple.SystemConfiguration 0x00007fff5e91111d SCDynamicStoreCopyComputerName + 409
21 com.apple.CFNetwork 0x00007fff512de753 -[NSHost localizedName] + 90
22 com.blizzard.heroesofthestorm 0x0000000103c5612e 0x100000000 + 63267118
23 com.blizzard.heroesofthestorm 0x0000000100da96bb 0x100000000 + 14325435
24 com.blizzard.heroesofthestorm 0x0000000100da7aad 0x100000000 + 14318253
25 com.blizzard.heroesofthestorm 0x0000000100dac673 0x100000000 + 14337651
26 com.blizzard.heroesofthestorm 0x000000010000c2a5 0x100000000 + 49829
27 dyld 0x0000000106bc3ac6 ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 420
28 dyld 0x0000000106bc3cf6 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 40
29 dyld 0x0000000106bbf218 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, char const*, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 330
30 dyld 0x0000000106bbe34e ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 134
31 dyld 0x0000000106bbe3e2 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 74
32 dyld 0x0000000106baf567 dyld::initializeMainExecutable() + 196
33 dyld 0x0000000106bb4239 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 7242
34 dyld 0x0000000106bae3d4 dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) + 453
35 dyld 0x0000000106bae1d2 _dyld_start + 54
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x00007fffb2d0d380 rcx: 0x00007ffeefbfa8c8 rdx: 0x0000000000000000
rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007ffeefbfa900 rsp: 0x00007ffeefbfa8c8
r8: 0x00007ffeefbfa790 r9: 0x00007ffeefbfa960 r10: 0x0000000000000000 r11: 0x0000000000000206
r12: 0x0000000000000307 r13: 0x0000000000000030 r14: 0x0000000000000006 r15: 0x000000000000002d
rip: 0x00007fff7a419b66 rfl: 0x0000000000000206 cr2: 0x00007fffb2cea168
Logical CPU: 0
Error Code: 0x02000148
Trap Number: 133
1 Like
Been having the same issue since it was on PTR.
MacBook Air
Processor: 1.7 GHz Intel Core i7
Memory: 8 GB 1600 MHz DDR3
Startup Disk: Macintosh HD
Graphics: Intel HD Graphics 5000 1536 MB
Thanks for all the info so far. Getting y’all to post the specs here is more of a way to do a quick visual parse for commonalities, but there’s nothing obvious in your system specs shared.
I looked over all of these and for some odd reason we’re unable to see your parent process 1, launchd, which is critical for a mac. I checked some of the other crashes and this is true for all of these. This may just be due to how early the crash happens, and I know this is going to sound like some generic troubleshooting. However, I’m sincerely interested if any of these work, though I don’t commonly recommend some of them for Mac systems.
We’re still trying to figure out what the common denominator here is but anything you try here that works or even just changes the crash behavior may help us narrow it down.
- Have you tried restarting your computer?
- Have you tried a combo update to the latest build for your version?
10.11.6
10.12.6
10.13.6
10.14.3 - Does it persist on a new administrator account or is it fixed there?
- Are there third party security programs running on your system outside of the native security/firewall for Mac OS? If so, does temporarily uninstalling these fix it?
Edited: Had the wrong link for 10.14.3 previously, sorry about that! Fixed.
This may be totally irrelevant, I’m no computer genius. But I remember having to change accessibility settings for Heroes so my mouse would work. I went to add Heroes to Full Disk Access on the Privacy menu and while that might not make a difference at all, it came up as the Diablo 3 launcher. It won’t come up as Heroes on the list. Any reason as to why it shows up as that? Sorry if this is completely irrelevant, just trying anything to play my favorite game again.
My macbook is updated and I reinstalled HOS
Same startup error. Just quits right away
1 Like
I just tried all the latest recommendations from the most recent blue post and nothing worked there either. That being said, my whole computer got kinda weird when i tried to boot it up with a new Admin user. It initially found the game, but after hitting play it just wouldn’t do anything. Wouldn’t even get an error message like on my normal profile. Not sure what to make of that
Legiticus,
That is indeed bizarre. Can you reinstall the game from the new profile and see if that changes anything? If not, and it gives you a crash code, please post that here. If you get a message about being unable to uninstall the game, try rebooting the PC again before re attempting the uninstall/reinstall.
Same here including the admin error not showing up.
- Restarting definitely does not work.
- Tried downloading Combo update for 10.14.3. Computer had to reset and then it automatically installs. Same error “Heroes quit unexpectedly” pops up upon launching.
- Tried using a “Guest” Account and when you try to Open HOTS, it actually does not give an error message, but just nothing happens for a few seconds while the “PLAY” button on the Battle. net app is greyed out with “Launching”. After those few seconds, the “PLAY” button just returns.
- No 3rd party Security programs on my system.
The app crashes in the ABI, I don’t see why any of your suggestions should work, they are just a waste of time for all the users who follow them, because the crash happens before any third party software has a chance to hook into the sys calls.
Playing with graphic settings is also a waste of time because the app crashes way before anything graphics related has been loaded.
I’m fairly sure that there is no workaround because when you look at the post-mortem you can clearly see that the localized host name is requested, then stored in a new variable but fails because __cxa_guard_acquire has been called before on the same guard object but without a release or abort. This is clearly a programming error and should normally be fairly easy to debug but since it happens in the ABI it might not be as straightforward. My guess is it’s a race condition between two different code paths, where the release call on the second code path comes too late.
6 Likes