-
Bug
-
Resolution: Fixed
-
P3
-
8u102, 10.0.1, 11, 12
-
b14
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8213064 | 11.0.2 | Sergey Bylokhov | P3 | Resolved | Fixed | b02 |
JDK-8216031 | 8u212 | Sergey Bylokhov | P3 | Resolved | Fixed | b01 |
JDK-8214659 | 8u211 | Sergey Bylokhov | P3 | Resolved | Fixed | b01 |
JDK-8211074 | 8u202 | Sergey Bylokhov | P3 | Closed | Fixed | b01 |
JDK-8212951 | 8u192 | Sergey Bylokhov | P3 | Closed | Fixed | b32 |
JDK-8221005 | emb-8u211 | Sergey Bylokhov | P3 | Resolved | Fixed | master |
sun.awt.X11.XToolkit.getScreenInsets() may be very slow
Our configuration is Java 8u102 32bit running on RedHat 6.8 with the remote
X11 display on a RedHat 6.8 machine with 3 monitors.
Dropdown menus, and comboboxes are taking over 2 seconds to respond to mouse
clicks.
- backported by
-
JDK-8213064 Swing apps are slow if displaying from a remote source to many local displays
-
- Resolved
-
-
JDK-8214659 Swing apps are slow if displaying from a remote source to many local displays
-
- Resolved
-
-
JDK-8216031 Swing apps are slow if displaying from a remote source to many local displays
-
- Resolved
-
-
JDK-8221005 Swing apps are slow if displaying from a remote source to many local displays
-
- Resolved
-
-
JDK-8211074 Swing apps are slow if displaying from a remote source to many local displays
-
- Closed
-
-
JDK-8212951 Swing apps are slow if displaying from a remote source to many local displays
-
- Closed
-
- duplicates
-
JDK-8004103 sun.awt.X11.XToolkit.getScreenInsets() may be very slow
-
- Closed
-
- relates to
-
JDK-8134669 Empty screen insets in Gnome 3, OEL 7 in multiscreen mode
-
- Resolved
-
-
JDK-8004103 sun.awt.X11.XToolkit.getScreenInsets() may be very slow
-
- Closed
-
-
JDK-4737732 Toolkit.getScreenInsets() doesn't work on Linux/GNOME
-
- Closed
-
-
JDK-8252349 Delete the "sun.awt.X11.checkSTRUT" property
-
- Resolved
-
- links to