You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to the Garbage Collector of Lua being not entirely flawless, and some hard to clean up relations in general, I guess this should be done manually.
Perhaps it could also help if I didn't make the Actor Class in NIL refer to a parent object, but only to the Map ID... This would surely do a lot of good, and could also help the garbage collector to set some things in order... Let's just say I messed a few things up BIG way....
The way things are going now can (and actually are) causing memory leaks on the bigger run (don't worry, everything gets cleaned up as soon as NALA ends, but still, I must get this sorted out!)
The text was updated successfully, but these errors were encountered:
I've removed a few internal NIL links, that were not really needed in the first place, and I've set this to some C# direct calls in stead. Since the Lua garbage collector (on which NIL relies) will always ignore direct C# links (it simply can't know they exist) this should make it easier on Lua to dispose the crap.... Now this does not guarantee 100% removal of all Kthura data, but at least the map itself should be disposed when no longer needed, and since that's the biggest memory eater by far, that was my primary concern.... Some tests do have to confirm this before I can close this though
- Issues with Dijkstra fixed
- A bit of optimization in the NIL glue code, this should take of PhantasarProductions/dyrt.net#27, but I cannot be sure yet!
Due to the Garbage Collector of Lua being not entirely flawless, and some hard to clean up relations in general, I guess this should be done manually.
Perhaps it could also help if I didn't make the Actor Class in NIL refer to a parent object, but only to the Map ID... This would surely do a lot of good, and could also help the garbage collector to set some things in order... Let's just say I messed a few things up BIG way....
The way things are going now can (and actually are) causing memory leaks on the bigger run (don't worry, everything gets cleaned up as soon as NALA ends, but still, I must get this sorted out!)
The text was updated successfully, but these errors were encountered: