- Joined
- Jan 13, 2017
- Messages
- 88
This is just a heads up for whoever uses Lua / TypescriptToLua or similar frameworks for their warcraft 3 maps.
The Lua GC is seemingly disabled.
Over in the hiveworkshop discord we did quite a bit of experimentation on this issue after i realised my map was leaking 0.6MB/s, but the leaks made absolutely no sense.
After 3 days of debugging we noticed that the GC is never called, memory is never cleaned up.
The memory simply keeps building up forever and __gc is never called.
Courtesy of @MindWorX for helping me test this.
(My image).
(Williams image).
If you want to test this for yourself, the test map is attached.
1.31 does not have this issue as it still uses the standard Lua incremental GC, but it also desyncs so.
The Lua GC is seemingly disabled.
Over in the hiveworkshop discord we did quite a bit of experimentation on this issue after i realised my map was leaking 0.6MB/s, but the leaks made absolutely no sense.
After 3 days of debugging we noticed that the GC is never called, memory is never cleaned up.
The memory simply keeps building up forever and __gc is never called.
Courtesy of @MindWorX for helping me test this.
(My image).
(Williams image).
If you want to test this for yourself, the test map is attached.
1.31 does not have this issue as it still uses the standard Lua incremental GC, but it also desyncs so.
Attachments
Last edited: