Crash, alik dolmen

vgabor

Never ever before had my game crashing in alik dolmens, and I have ran them gazzilion times... Maybe now it caused by the memory handling update from the last patch?

Process:               eso [83696]
Path:                  /Applications/Games/*/eso.app/Contents/MacOS/eso
Identifier:            eso
Version:               1.0.0 (1.0.0)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           eso [83696]
User ID:               501

Date/Time:             2019-10-28 09:36:15.951 +0000
OS Version:            Mac OS X 10.14.6 (18G95)
Report Version:        12
Bridge OS Version:     3.0 (14Y904)
Anonymous UUID:        BADC6FD7-23ED-705B-3B1D-BB3CE68B326B

Sleep/Wake UUID:       1285B296-5A9C-4B20-AC3F-D32D66A186BE

Time Awake Since Boot: 130000 seconds
Time Since Wake:       48000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000018
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [83696]

VM Regions Near 0x18:
--> 
    __TEXT                 00000001092cf000-000000010dd28000 [ 74.3M] r-x/rwx SM=COW  /Applications/Games/*/eso.app/Contents/MacOS/eso

ID   Vend/Dev
a393 687f1002
Seconds Ago   ID   Type
   210000.0   a393 Attach

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.zenimaxonline.eso         	0x000000010a90b0fc mvkUpdateDescriptorSets(unsigned int, VkWriteDescriptorSet const*, unsigned int, VkCopyDescriptorSet const*) + 76
1   com.zenimaxonline.eso         	0x000000010b0c4d00 ZoEffectTechniqueVk::BindResources(ZoDeviceContext*) + 1186
2   com.zenimaxonline.eso         	0x000000010b06ec4f ZoRenderManager::DrawIndexedPrimitive(ZoRenderDefs::PRIMITIVE_TYPE, int, unsigned int, unsigned int, unsigned int, unsigned int, unsigned int*) + 41
3   com.zenimaxonline.eso         	0x000000010b0795a9 ZoRenderable::DrawPrimitive() + 181
4   com.zenimaxonline.eso         	0x000000010b0295ff ZoMaterialManager::RenderRenderable(ZoRenderable*) + 453
5   com.zenimaxonline.eso         	0x000000010b09f403 ZoWaterPass::DrawWaterTransparencyListRanged(ZoLockedAddArray<ZoRenderList::RenderListEntry, 1024u, false> const&, unsigned int, unsigned int) + 95
6   com.zenimaxonline.eso         	0x000000010b09ebef ZoWaterPass::WaterTransparencyPass(ZoDeferredRenderingList*) + 395
7   com.zenimaxonline.eso         	0x000000010b09e429 ZoWaterPass::Render(ZoDeferredRenderingList*) + 69
8   com.zenimaxonline.eso         	0x000000010b065af5 ZoRenderGraph::Render(ZoDeferredRenderingList*) + 261
9   com.zenimaxonline.eso         	0x00000001096f0f5c ClientWorld::Render() + 326
10  com.zenimaxonline.eso         	0x0000000109318c82 OSRender() + 605
11  com.zenimaxonline.eso         	0x000000010931af1c -[GameClient macRun] + 309
12  com.zenimaxonline.eso         	0x000000010931b852 -[GameClient platformMainLoop] + 2164
13  com.zenimaxonline.eso         	0x000000010931ab8b -[GameClient mainLoop] + 61
14  com.zenimaxonline.eso         	0x000000010931aa93 -[GameClient applicationDidFinishLaunching:] + 668
15  com.apple.CoreFoundation      	0x00007fff47d26b96 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
16  com.apple.CoreFoundation      	0x00007fff47d26b10 ___CFXRegistrationPost_block_invoke + 63
17  com.apple.CoreFoundation      	0x00007fff47d26a7a _CFXRegistrationPost + 404
18  com.apple.CoreFoundation      	0x00007fff47d2ef28 ___CFXNotificationPost_block_invoke + 87
19  com.apple.CoreFoundation      	0x00007fff47c978b4 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1642
20  com.apple.CoreFoundation      	0x00007fff47c96c67 _CFXNotificationPost + 732
21  com.apple.Foundation          	0x00007fff49f1caab -[NSNotificationCenter postNotificationName:object:userInfo:] + 66
22  com.apple.AppKit              	0x00007fff452c0fc4 -[NSApplication _postDidFinishNotification] + 312
23  com.apple.AppKit              	0x00007fff452c0917 -[NSApplication _sendFinishLaunchingNotification] + 208
24  com.apple.AppKit              	0x00007fff452bea6b -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 552
25  com.apple.AppKit              	0x00007fff452be6bb -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 688
26  com.apple.Foundation          	0x00007fff49f66700 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 286
27  com.apple.Foundation          	0x00007fff49f6657d _NSAppleEventManagerGenericHandler + 102
28  com.apple.AE                  	0x00007fff48ee8397 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 1815
29  com.apple.AE                  	0x00007fff48ee7c29 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 41
30  com.apple.AE                  	0x00007fff48ee7b01 aeProcessAppleEvent + 414
31  com.apple.HIToolbox           	0x00007fff46f2b8b7 AEProcessAppleEvent + 54
32  com.apple.AppKit              	0x00007fff452baabd _DPSNextEvent + 1935
33  com.apple.AppKit              	0x00007fff452b948b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
34  com.apple.AppKit              	0x00007fff452b35a8 -[NSApplication run] + 699
35  com.zenimaxonline.eso         	0x000000010931c5fa main + 200
36  libdyld.dylib                 	0x00007fff73c193d5 start + 1

ZOS_Bill

@vgabor

Was this a one time crash in alik dolmens or is it repeating?

If the crash is repeating, is there a certain area or action triggering the crash?

vgabor

@ZOS_BillE One time yesterday so far, and haven't repeated since so there's nothing to match with to find any pattern... It happened after the dolmen boss died and before the chest appeared, but looking at the calltrack above, it had probably nothing to do with the actual location, just something with the rendered resource descriptor handling code went wrong. My guess at the look of it, that it tried to access a resource descriptior which wasn't there...

In the weekend I added an eGPU (razer x core + msi amd radeon vega 56) to my 13'' macbook pro and did increase the video quality from low/medium to high in the game video settings and switched on some previously turned off options (like bloom, sunlight, and such), so it is very possible that with the new higher video quality the code now hitting previously unused code parts and one of those caused the problem...

(As a side note, the eGPU works well with the game, hugely increased both video quality and fps. The game now seems to be bound only by the 13'' macbook pro cpu, as increasing/decreasing the video settings has little to no effect on the performance anymore.)