Closed ianthehenry closed 10 years ago
Running the moving-square example on OS X was leaking hundreds of megs of memory per second! Appears a destroyTexture call managed to slip away into some dark night.
destroyTexture
Woops! Thank you very much, was a result of changing it from the unreleased SDL2 bindings to the released low-level ones.
Running the moving-square example on OS X was leaking hundreds of megs of memory per second! Appears a
destroyTexture
call managed to slip away into some dark night.