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
Hi all;
I am trying to debug a RAM issue with my app (java app with swing and openwebstart).
I am running openwebstart 1.7 and java 17 (tumerin)
I took a heap dump when I have RAM issue and I see the report on eclipse MAT (memory analyzer tool) that instances of class JavaConsole$JavaConsoleHolder are taking most of the heap.
is this to be expected? not sure what this class does and why it takes so much space.
diving deeper looks like console messages are taking all the space inside this object?
any guidence will help
thanks
PS: we are using log4j2.17.1 which I noticed was flagged in another thread here as problematic but I am not sure if for the same reason
The text was updated successfully, but these errors were encountered:
Workaround 1: Enable the console and check if you application writes to stdout and try to avoid this
Workaround 2: set the console to disabled (instead of hidden)
Workaround 3: write a cleanup-thread that peridically clears the map (can only be done by reflection)
Hi all;
I am trying to debug a RAM issue with my app (java app with swing and openwebstart).
I am running openwebstart 1.7 and java 17 (tumerin)
I took a heap dump when I have RAM issue and I see the report on eclipse MAT (memory analyzer tool) that instances of class JavaConsole$JavaConsoleHolder are taking most of the heap.
is this to be expected? not sure what this class does and why it takes so much space.
diving deeper looks like console messages are taking all the space inside this object?
any guidence will help
thanks
PS: we are using log4j2.17.1 which I noticed was flagged in another thread here as problematic but I am not sure if for the same reason
The text was updated successfully, but these errors were encountered: