Out of memory errors caught by Jmol are not detected and acted on by Jalview

Loading large structures into Jmol (e.g. a viral capsid reconstruction) when insufficient memory is available causes Jmol to report the following error on the console output:
viewer handling error condition: java.lang.OutOfMemoryError: Java heap space

Jalview doesn't detect this error message on the console, and if it occurred whilst the structure was being loaded, then it simply waits forever for the 'File loaded' event to be raised. This leaves the structure displayed in Jmol with default rendering style, and no listing of the structure's chains in the View menu of Jalview's JmolApp window.