JDK-8350766 : Reduce the chances of sending SIGQUIT too early in VM attach implementation of macosx
  • Type: Enhancement
  • Component: core-svc
  • Sub-Component: tools
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: os_x
  • Submitted: 2025-02-26
  • Updated: 2025-03-18
  • Resolved: 2025-03-18
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 25
25Resolved
Related Reports
Duplicate :  
JDK-8344671 - Few JFR streaming tests fail with application not alive error on MacOS 15
Description
Unlike the Linux implementation, the current implementation of VM attach mechanism on macosx sends a SIGQUIT to the target process without additional checks to verify that the target JVM process has reached a state where it can handle the SIGQUIT. It has been reported recently in a few issues that because of this, the target process may receive the SIGQUIT when it's still in the early stages of launching and upon receiving that signal, the process terminates/crashes. https://bugs.openjdk.org/browse/JDK-8344671 has details about such problems.

If feasible, it would be better to introduce some checks, before sending the SIGQUIT to the target JVM so that these issues can be prevented.
Comments
[~lcable] Only JBS issues with an associated changeset should be marked as Fixed. This is a duplicate of JDK-8344671 as that is where the fix is being done.
18-03-2025