Description
Error reporting may hang. This may happen if the original crash left a mutex hanging, or if the reporting step is just slow.
For example, for a while we observed stack printing on Solaris to be exceptionally slow if the VM binary resided on an NFS share, or printing of shared object locations on AIX was sluggish.
If these cases indicate bugs in the VM, they should of course be fixed, but it would be very helpful if error reporting was more robust in the face of hangs - similar to how it handles secondary crashes during error reporting. So, error reporting steps should be interruptible, and should be interrupted if they take too long.
For example, for a while we observed stack printing on Solaris to be exceptionally slow if the VM binary resided on an NFS share, or printing of shared object locations on AIX was sluggish.
If these cases indicate bugs in the VM, they should of course be fixed, but it would be very helpful if error reporting was more robust in the face of hangs - similar to how it handles secondary crashes during error reporting. So, error reporting steps should be interruptible, and should be interrupted if they take too long.
Attachments
Issue Links
- relates to
-
JDK-8302073 Specifying OnError handler prevents WatcherThread to break a deadlock in report_and_die()
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-