For regular Java-managed direct buffers, JME does not need to clean them up as the GC will clean them up.
For any memory that Java is not allocating, special support (like PhantomReference) will have to be used to make sure to free the native memory.
I think until we switch to using jme3-alloc (in JME 3.7), for JME 3.6.1 we should either switch to using PrimitiveAllocator on Android or use PhantomReference in AndroidNativeBufferAllocator to free memory. (similar to the jme3-lwjgl3 buffer allocator)
For regular Java-managed direct buffers, JME does not need to clean them up as the GC will clean them up.
For any memory that Java is not allocating, special support (like PhantomReference) will have to be used to make sure to free the native memory.
I think until we switch to using
jme3-alloc(in JME 3.7), for JME 3.6.1 we should either switch to using PrimitiveAllocator on Android or use PhantomReference in AndroidNativeBufferAllocator to free memory. (similar to thejme3-lwjgl3buffer allocator)