Project

General

Profile

Bug #6006

JVM process failures while executing the swing client

Added by Sergey Ivanovskiy over 2 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:

hs_err_pid_20220121.zip (58.7 KB) Sergey Ivanovskiy, 01/24/2022 02:12 PM

History

#1 Updated by Sergey Ivanovskiy over 2 years ago

Added logs for the observed JVM crashes.

#2 Updated by Greg Shah over 2 years ago

It is my understanding that these failures have occurred sporadically while running a customer's converted GUI application using the Swing GUI client. As far as I understand, there is no known recreate.

Two of the failures occur on the VMThread when the JVM is exiting and some processing is occurring in the native code of the JVM. The VMThread is a "housekeeping" thread which handles a range of things. The failure is a segment violation/protection fault which means that some native memory was accessed which the JVM process was not allowed to access. Normally, this is the result of incorrect pointer math or just an invalid pointer value in the native code. There is no indication that this is related to FWD in any way.

The remaining issue occurs on the AWT-EventQueue-1 thread, also from native code and it is also a segment violation/protection fault. This one occurs in the native code called from the Java code sun.awt.X11.XlibWrapper.XChangePropertyImpl. AWT operates with many classes that have "native peer code" which implements the low level parts of the AWT UI processing. Something is failing there. It is definitely a JVM bug since it should not be possible to cause this kind of failure. However, in this case it could be due to something we are doing with AWT.

Also available in: Atom PDF