On Wed, 3 Aug 2022 07:17:51 GMT, Thomas Stuefe <stu...@openjdk.org> wrote:
> Happens when the main thread detaches itself upon VM exit. VM attempts to > release OMs that are owned by the finished main thread (side note: if that is > the sole surviving thread, maybe that step could be skipped?). That happens > before DestroyVM, so OM final audit did not yet run. > > Problem here is the OM in use list is circular (and very big, ca 11mio > entries). > > I was able to reproduce it with a fastdebug build in 1 out of 5-6 runs. Also > with less benchmark cycles (-r 3). Hi Thomas, thanks for testing and reporting the issue. I just pushed an improvement (and simplification) of the monitor-enter-inflate path, and cannot seem to reproduce the problem anymore. Can you please try again with the latest change? ------------- PR: https://git.openjdk.org/jdk/pull/9680
