Hi Erwan,
Here is my answer again. I cut out all of the prior post history so it
should make it though.
I have found that many things in OJ use a lot of temporary memory, but
don't trigger the garbage collection so the Committed Memory label often
gives a pessimistic view. There is a one second timer in
com.vividsolutions.jump.workbench.ui.WorkbenchFrame that updates the
Committed Memory display constantly.
To fix this issue, we would need to use System.gc(), however it would not
be advisable to do this inside the timer event that updates the Committed
Memory label because it might slow down any threads that are running.
Ideally, you would do it when OJ is idle, something I have found extremely
difficult to determine.
Here is an alternative solution. The Committed Memory label could be
converted to a more dynamic indicator by generating a color coded bar graph
(green, yellow, red) as the remaining free memory decreases. This allows the
user to focus on the most important thing about memory usage: when free
memory is low, OJ slows down due to frequent garbage collections.
If you wanted to know exact figures, you could always use the Info tab on
the Help->About box. The About method gives a much more accurate static
picture of memory usage since it includes a garbage collect button.
Does anyone have an opinion on this possible change?
regards,
Larry Becker
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
