zones with a lot of achievements in the minilist or opening the Dynamic categories to achievements are tripping the CPU and mem usage CPU usage is of 90-100% and freeze the client, when happen a LUA error the cpu and ram usage return to normal
milotic opened this issue ยท 2 comments
Which flavo(u)r(s) of WoW are you using?
Retail
Which server realm(s) are you in?
US
What build number of WoW?
11.2
Which version of ATT?
Latest alpha
What build number of ATT?
4.6.0
What isn't working? What was supposed to happen?
ATT is eating like galactus resources in maps with a lot of achievements in the mini list or try opening the Dynamic category of achievements have a mem and cpu seizure, when the lua error happen the resouces return to a normal value
Screenshot
Steps to reproduce the behavior.
stay in a place with a lot of achievements or try load the Dynamic categories att start to eat resources
Are you experiencing any lua errors?
1x AllTheThings/src/DataHandling.lua:36: script ran too long
[AllTheThings/src/DataHandling.lua]:36: in function <AllTheThings/src/DataHandling.lua:34>
[AllTheThings/src/DataHandling.lua]:255: in function <AllTheThings/src/DataHandling.lua:179>
[AllTheThings/src/DataHandling.lua]:287: in function <AllTheThings/src/DataHandling.lua:273>
[AllTheThings/src/DataHandling.lua]:249: in function <AllTheThings/src/DataHandling.lua:179>
[AllTheThings/src/DataHandling.lua]:287: in function <AllTheThings/src/DataHandling.lua:273>
[AllTheThings/src/DataHandling.lua]:249: in function <AllTheThings/src/DataHandling.lua:179>
[AllTheThings/src/DataHandling.lua]:287: in function <AllTheThings/src/DataHandling.lua:273>
[AllTheThings/src/DataHandling.lua]:249: in function <AllTheThings/src/DataHandling.lua:179>
[AllTheThings/src/DataHandling.lua]:287: in function <AllTheThings/src/DataHandling.lua:273>
[AllTheThings/src/DataHandling.lua]:249: in function <AllTheThings/src/DataHandling.lua:179>
[AllTheThings/src/DataHandling.lua]:287: in function <AllTheThings/src/DataHandling.lua:273>
[AllTheThings/src/DataHandling.lua]:249: in function <AllTheThings/src/DataHandling.lua:179>
[AllTheThings/src/DataHandling.lua]:287: in function <AllTheThings/src/DataHandling.lua:273>
[AllTheThings/src/DataHandling.lua]:249: in function <AllTheThings/src/DataHandling.lua:179>
[AllTheThings/src/DataHandling.lua]:347: in function 'TopLevelUpdateGroup'
[AllTheThings/src/UI/Retail Window Logic.lua]:149: in function <...eAllTheThings/src/UI/Retail Window Logic.lua:120>
[AllTheThings/src/UI/Retail Window Logic.lua]:1041: in function 'BaseUpdate'
[AllTheThings/AllTheThings.lua]:4312: in function <AllTheThings/AllTheThings.lua:4311>
[AllTheThings/src/UI/Retail Window Logic.lua]:1042: in function <...eAllTheThings/src/UI/Retail Window Logic.lua:1042>
[AllTheThings/lib/Callback.lua]:22: in function <AllTheThings/lib/Callback.lua:16>
Locals:
(*temporary) =
costTotal = 0
upgradeTotal = 0
parent =
}
g =
}
npcID = 96759
total = 7
progress = 2
encounterID = 1663
}
(*temporary) =
visible = true
total = 1
upgradeTotal = 0
b = 1
parent =
}
sourceID = 80120
f = 6
modID = 2
lvl = 40
modItemID = 133769.002000
costTotal = 0
progress = 0
itemID = 133769
}
(*temporary) = "script ran too long"
Anything else?
No response
@milotic have you noticed this still an issue on latest ATT? There's been a lot of fixes and improvements since this report and I haven't personally noticed something like this
