Originally Posted by Garkin
[...]
new event: EVENT_LUA_LOW_MEMORY
and when it occurs, it shows this error message:
"Lua is reaching its memory limit. You should consider disabling some addons and reloading the UI."
|
I'm assuming even well-behaved add-ons aren't expected to listen and effectively reaction to this event?
With Lua's garbage collection, can you free much memory usage from within an add-on? Free up a few tables by setting them to
nil? Set any textures to
nil or unload otherwise free them?
I don't know if an add-on can disable or free itself.
I guess you can un-register for events, or even set functions to
nil but I don't thing that's enough to kill an add-on in memory. (Functions being a first-class data type / object)
Not intended to be dismissive of Lua or the versatility of automatic GC. Just surprised to see it, but I'd guess its visible unintentionally because it
is part of the Add-on API / support.