Description
Adding to the Linux woes #353, #367, we observe the following on RHEL 7.6 computers with NVIDIA graphics cards (nvidia-smi reports version 340.107).
On the computer, running multiple copies via ssh or a ThinLinc remote desktop is fine.
Starting multiple instances at the physical desktop causes the second, 3rd or 4th copy to be very slow.
That sluggish instance doesn't need to execute any display. Simply trying to open the "File" menu will
- be very slow
- result in using one CPU core for a while
- often lock the complete desktop
When attaching JProfiler, the JVM doesn't consider itself using much CPU at those times. Instead, the UI thread is blocked in GlassScene.waitForRenderingToComplete(), basically calling the GTK graphics library.
Sometimes there are these types of messages in /var/log/messages suggesting a graphics driver problem:
kernel: NVRM: GPU at PCI:0000:01:00: GPU-95a676e2-3d89-3607-cd49-b7ad9d23f9f8
kernel: NVRM: Xid (PCI:0000:01:00): 13, Graphics Exception: ChID 0005, Class 00005039, Offset 00000100, Data 00000000
After killing the problematic instance of phoebus, the X server might be stuck using a CPU core, and the only way to fix it is
sudo systemctl restart display-manager
Adding this to the JVM options, i.e. disabling accelerated graphics as in principle supported by the NVIDIA driver, seems to avoid the issue:
-Dprism.order=sw