Thank you Alan, that was helpful.
Until the sysadmins make the fixed version of Firefox available, is there any
manual step one could take to reduce the ridiculously large Xvnc memory
footprint (other than the obvious heavy-handed approach of killing the
vncserver job and restarting it) ?
Wondering if I'm the only lucky one to experience this:
Invoke vncserver to start an Xvnc session.
Connect to the Xvnc session via vncviewer.
Invoke firefox within the Xvnc session.
At this point, the memory consumption of the Xvnc job is around 20 MB,
which about par for a typical Xvnc memory
