Yeah, I've noticed that you can't use HeapTrace or any of the other stuff to "debug" the PNG's that are loaded. While there may be a leak or an overrun/override I can't find it. Running the code in a VM and monitoring actual memory usage there are no leaks found (same amount of free memory before as after the run), so I'm a bit lost.

Anyone finds something I'd love to hear it. The "errors" thrown move depending on machine and version you compile in, so this points more to a Memory Overrun than it does a typical leak.

- Jeremy