In out production environment, we encountered a direct memory oom issues caused by the direct buffer not released in time.
After carefully checked the code, it seems that the some methods of SnappyDecompressor/SnappyCompressor would not release the direct buffer manually. If too much direct memory allocated and no GC happens, this bug may result in direct memory oom.
Moreover, if the `-XX:+DisableImplicitGC` jvm option is specified, the direct memory oom would happen easily for large datasets.
Seems that the problem still exist in the latest code.