On Mon, 17 Jan 2022 09:00:25 GMT, Kevin Walls <kev...@openjdk.org> wrote:
> > I propose a simpler and more robust way to fix it though > > Great, this is the kind of thing I was heading towards with the conversation > in the bug text. Although not sure why I could not reproduce the problem, > with various different JDK versions. Ah, I missed your conversation. I reproduced this by adding a delay during initialization and sending sigquit manually. The bug is not restricted to jcmd, sigquit handling is broken during initialization. Folks tend to send sigquit to unresponsive VMs to get thread dumps, so coring is unfortunate (another reason not to fix it in jcmd itself). Cheers, Thomas ------------- PR: https://git.openjdk.java.net/jdk/pull/7003
