That doesn't say GC is "kind of random".
GC is automatically called every few seconds, as can be seen if you constantly draw GCMemAlloced() to screen during execution.
If you do get that paranoid about it, you can turn off automatic garbage collection and call GCCollect manually. Personally, I wouldn't bother though.
Oh, and anybody who says they've got memory leaks in their program most likely has bugs in their own code, rather than there being something wrong with Blitzmax's garbage collection. I don't recall any reported problems with it.
GC is automatically called every few seconds, as can be seen if you constantly draw GCMemAlloced() to screen during execution.
If you do get that paranoid about it, you can turn off automatic garbage collection and call GCCollect manually. Personally, I wouldn't bother though.
Oh, and anybody who says they've got memory leaks in their program most likely has bugs in their own code, rather than there being something wrong with Blitzmax's garbage collection. I don't recall any reported problems with it.