Hi Eddie,
We took a look at workspace file that you sent and unfortunately, there wasn't much information that we could use. There were some exceptions but it unclear whether they are contributing to high memory usage. We also tried to reproduce high memory usage and eventual crash, but have not run into this issue. I have observed that if I open and then close .cfg file then heap status monitor will appear to show a leak (i.e. heap memory keeps increasing). However, after a few minutes (I have not been able to determine exact time or trigger) that memory seems to be freed up. Even after I close .cfg editor and click on Trash icon to invoke GC, it still does not change much. However, after a few minutes it seems to free up heap to roughly what it was before I opened .cfg file.
It maybe difficult to reproduce this on our side. One thing that I can think of that might help is doing a heap dump when you see that high memory usage being shown in heap monitor. There are some tools that can analyze heap dumps and provide more useful information. e.g. which classes/objects have allocated most memory and do analysis if there are candidate memory leaks.
Setting this up would take a bit of time, thus I am not sure if this is something that you would be willing to do. I would also need to setup a temporary ftp site as the heap dump file will be roughly the size of your java heap. i.e. much larger than an e-mail or forum post could handle.
Please let me know if you can help us tracking this down.
Thanks,
Martin