You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There appears to be a consistent, large memory use by the class CustomClassloaderJavaFileManager (16% of bytes arrays accoording to heapdump), coming from the class com.dexels.navajo.compiler.tsl.custom.CustomJavaFileObject. The cause appears to be a "double" allocation of both a byte array together with a file in tmpDir, where the byte array appears to not be used anymore.
Further investigation of (memory) performance improvement here might be useful.
The text was updated successfully, but these errors were encountered:
There appears to be a consistent, large memory use by the class
CustomClassloaderJavaFileManager
(16% of bytes arrays accoording to heapdump), coming from the classcom.dexels.navajo.compiler.tsl.custom.CustomJavaFileObject
. The cause appears to be a "double" allocation of both a byte array together with a file in tmpDir, where the byte array appears to not be used anymore.Further investigation of (memory) performance improvement here might be useful.
The text was updated successfully, but these errors were encountered: