A DESCRIPTION OF THE PROBLEM :
When using libumem as memory allocator, and enable memory audit, there are a lot of leaks coming from

fffffb7ffeca5028 1 fffffb7f71a6d6c0 libjvm.so`__1cCosGmalloc6FLnKMemoryType_rknPNativeCallStack__pv_+0xb6
fffffb7ffeca5028 1 fffffb7f7509ea80 libjvm.so`__1cCosGmalloc6FLnKMemoryType_rknPNativeCallStack__pv_+0xb6
fffffb7ffeca5028 1 fffffb7f7499cf00 libjvm.so`__1cCosGmalloc6FLnKMemoryType_rknPNativeCallStack__pv_+0xb6
fffffb7ffeca5028 1 fffffb7f64ceaf00 libjvm.so`__1cCosGmalloc6FLnKMemoryType_rknPNativeCallStack__pv_+0xb6
fffffb7ffeca5028 1 fffffb7f71d4b6c0 libjvm.so`__1cCosGmalloc6FLnKMemoryType_rknPNativeCallStack__pv_+0xb6
fffffb7ffeca5028 1 fffffb7f7f6fee40 libjvm.so`__1cCosGmalloc6FLnKMemoryType_rknPNativeCallStack__pv_+0xb6
fffffb7ffeca5028 1 fffffb7f64c0fa80 libjvm.so`__1cCosGmalloc6FLnKMemoryType_rknPNativeCallStack__pv_+0xb6
fffffb7ffeca5028 1 fffffb7f7f7ba780 libjvm.so`__1cCosGmalloc6FLnKMemoryType_rknPNativeCallStack__pv_+0xb6

This could be caused by changeset
changeset: 8504:f8a45a60bc6b
summary: JDK-8174962: Better interface invocations