I belive there is currently a memory leak issue related to *when* you call flushmem. i.e. call it in the wrong place and it will never free certain objects.
It's not a memory leak as such, but rather a limitation in the design of the garbage collector. The BlitzMAX garbage collector does not find root objects like traditional garbage collectors do. Instead it works by counting references.They way I understand it is, when you invoke flushmem the garbage collector will not be able to tell if references above it in the heap represent alive or dead objects, so will simply assume that they're alive, only collecting dead references below it.