Do Gideros call collectgarbage() occasionaly?

Nascode

As questioned. And If Gideros calls collectgarbage behind the scene, could we know the implementation detail? Is there any optimization applied?

Today i saw lua gc optimization articles http://www.altdevblogaday.com/2011/07/23/predictable-garbage-collection-with-lua and http://bitsquid.blogspot.com/2011/08/fixing-memory-issues-in-lua.html those articles made me wonder about Gideros's lua gc

tagging @atilim

atilim

Gideros only calls collectgarbage() when there is a memory warning (both on iOS and Android).

Here I can recommend a strategy like:
1. Disable garbage collection while in the middle of the game.
2. Call collectgarbage() at the beginning of a level, at the end of a level, when user pauses the game, when user dies, etc.

Nascode

@atilim ok, so we should use collectgarbage("stop") to stop the gc? Or is the gc stopped by default at start?

atilim

@nascode, GC is enabled by default and yes you should call collectgarbage("stop") to stop it.

Also there is a small detail: Assume that you stop the garbage collector by calling collectgarbage("stop"). If you call collectgarbage() to perform a full garbage-collection cycle, garbage collection starts again.