Will RenderableManger and ByteBuffer cause memory leak?

[yicong123456]

I used filament for 3d development on android and I got this error: signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
2023-10-26 21:24:58.500 30537-30537 DEBUG pid-30537 A Abort message: 'JNI ERROR (app bug): global reference table overflow (max=51200)global reference table dump:
Last 10 entries (of 51195):
51194: 0x70feadd0 java.lang.Class<java.util.concurrent.Executor>
51193: 0x7140a5a0 java.lang.Class<android.os.Handler>
51192: 0x12eeaaa8 byte[] (168 elements)
51191: 0x12eeaa78 java.nio.HeapByteBuffer
51190: 0x70feadd0 java.lang.Class<java.util.concurrent.Executor>
51189: 0x7140a5a0 java.lang.Class<android.os.Handler>
51188: 0x142230c0 byte[] (3048 elements)
51187: 0x14223090 java.nio.HeapByteBuffer
51186: 0x1370b278 java.lang.Class<com.google.android.filament.NioUtils>
51185: 0x70feadd0 java.lang.Class<java.util.concurrent.Executor>
Summary:
I did not write native code myself, seems that I did not clean up some resources while using filament and cause memory leak. I used RenderableManager.builder() every time I got data from backend and also I used ByteBuffer. May wanna ask if it is the reason caused the problem and if it is how to release the resource correctly. Thanks so much!