-
Notifications
You must be signed in to change notification settings - Fork 104
Description
Which flavo(u)r of WoW are you using?
Classic Era
Which server realm are you in?
CN
WoW Client Build
3.80.0
WoW Event
Other
WoW Client Language
zhCN
ATT Version
Latest release
ATT Build Number
4.7.6
Describe the Bug
Hello,
I have found a crash in WoW Classic (Wrath Classic) that seems to be triggered by AllTheThings (ATT) in combination with Atlas.
Environment:
WoW Classic (Wrath Classic) 3.80.0.64393
Windows 10 x64
AllTheThings version: 4.7.6
Suggested fix:
ATT could safely skip or ignore items that no longer exist on the server to prevent client crashes.
Thank you for looking into this!
Screenshot
disable ATT no error:
enable ATT.client crash:
Steps to Reproduce
Steps to reproduce:
Enable AllTheThings.
Open Atlas and navigate to a dungeon/raid loot table.
Scroll to items that no longer exist on the Titan WotLK server (they still appear in Atlas's loot list but are missing on the server).
Observed behavior:
When the mouse hovers over these missing items in the Atlas loot list, the client crashes.
Crash report shows an ACCESS_VIOLATION in WowClassic.exe.
Example crash summary:
The memory could not be "read".
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007ff7be1146b1>("WowClassic.exe") <- DBG-ADDR<00007ff7c00d8498>("WowClassic.exe") <- DBG-ADDR<00007ff7c00cd9ac>("WowClassic.exe") DBG-OPTIONS<>)
Additional information:
Disabling ATT prevents the crash.
The issue seems to happen because Atlas still includes items that the Titan WotLK server has removed. ATT attempts to scan all items in the list, including these missing ones, which triggers the crash.
Lua Errors
No response
Additional Context
No response