Closed plusmouse closed 4 months ago
I have the cursed client. I refrained from updating the sets in any way, fearing to lose the reproducibility of this bug. Last time I checked it still caused crashes. I remain available for any information on the character
Update on what causing the crash. I have been able to reproduce the crash also for other equipment set, the condition is that the set needs to contain all 19 items (tabard and shirt included). At that point calling
\dump C_EquipmentSet.GetItemLocations(id)
causes an apple crash report.
I am on an M1 mac.
This issue has a another affected user https://github.com/moody/Dejunk/issues/190 They are also on a Mac, classic and have an equipment set with 19 items in it.
I'll add my two cents, the Equipment Manager API appears to have been re-worked in Legion, where at that time, it was impossible to have more than 18 items equipped due to the removal of the secondary weapon slot in MoP. I would guess thats where the issue comes from. The crash log mentions that WoW reports a "stack buffer overflow" as the reason for crashing.
I've had quite a few users over the years affected by this as well. For now, I've disabled use of the API in WotLK, but a fix for this hard crash would be great :)
My forum post about this finally got a blue response, hopefully it can get figured out.
Update: It doesn't crash for Intel Macs apparently. Only ARM Macs are affected.
That's great news :)
Fixed in pending - or possibly even most recently deployed - build.
Fixed in the build deployed today.
Running
on their client crashes the game. This happens on a clean login, and at any point during the session.
Dumping the set ids gives
Notably running GetItemLocations on the second or third equipment set does NOT cause a crash, it is exclusively the first equipment set.
The info for the problematic equipment set is
and
Looking at the items none appear weird, mostly phase 3 and phase 4 equipment.
I've tested the equipment set APIs on my device and despite locking items, destroying items, putting items in banks, vendoring items none of it triggers a crash when requesting the item locations of the set using the items.