There are a few calls to this scattered around the codebase, mostly after OutOfMemoryError, but also in
I’m not sure there is ever a good reason to call this routinely. I noticed that if you open a large alignment, then open any panel (say Feature Settings, or PCA Chooser) and then close it, there is a very noticeable pause, and jvisualvm shows a big spike in CPU and GC. It seems to behave like a blocking call to gc() rather than the usual background thread behaviour. Commenting out the call in Desktop.internalFrameClosed() removes the delay. Should we get rid of it?
The University of Dundee is a registered Scottish Charity, No: SC015096
Jalview Computational Scientist
The Barton Group
Division of Computational Biology
School of Life Sciences
University of Dundee, Dundee, Scotland, UK
We’re Scottish University of the Year again!
The Times / Sunday Times Good University Guide 2016 and 2017