The need to .close() colours about jaylib HOT 6 CLOSED

All of the Raylib struct classes implement Autoclosable, not just Color. Implementing Autoclosable does not mean you must close them.

As for what happens if you do close them, you would need to check with JavaCPP, but I assume it releases the native memory allocated by the struct.

C structs are not stored on the garbage collected Java heap, they are stored on the native heap.

from jaylib.

If you’re worried what happens if you don’t close() them yourself, I expect that when the object is GCed there is a finalize() method that calls close().

from jaylib.

Good. I removed the .close()'s from my code, and there was no performance decrease, despite colours being created on each frame.

from jaylib.

I asked because Eclipse gives a warning that it should be closed.

from jaylib.

It’s best not to create objects every frame. Maybe use an object pool.

from jaylib.

Different program but similar issue, I notice you are calling malloc and sprintf in your main loop here, which might explain why your C benchmark is slower than some of the others https://codeberg.org/glowiak/rl-bunnymarks/src/branch/master/c/bunny.c

from jaylib.