Debugging Addon Memory Leaks?
dug into Aloft, using OptionHouse, at the behest of a user, and did indeed discover a slow memory leak (about 187Kb/hour).
Aloft makes rigorous/extensive use of recycling, always checks to see if things are already allocated before allocating them, and etc. as far as i know, there are no tools for tracking memory management in LUA (as embedded in the WoW client).
can anyone sanity check whether 187Kb/hour is "normal"? does anyone have any suggestions, obvious things to look for in the use of the Blizzard API, links to resources (discussion threads/etc), or anything else of the kind?
thanks.
|