Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8283270

[11u] broken JRT_ENTRY_NO_ASYNC after Backport of JDK-8253795

    XMLWordPrintable

Details

    • b07

    Description

      "runtime/Thread/StopAtExit.java" fails intermittently with "exception oop already set" since backport of JDK-8253795 (commit https://github.com/openjdk/jdk11u-dev/commit/eb0708f75aa3c196e41014addfaa5667fd940cc2 ).

      JRT_ENTRY_NO_ASYNC was changed to use ThreadInVMfromJava (instead of ThreadInVMfromJavaNoAsyncException) which causes async Exceptions (ThreadDeath) to show up at places where we can't handle them (e.g. forward_exception Runtime1 stub).

      Attachments

        Issue Links

          relates to

          Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8281830 Implementation of JEP 391: macOS/AArch64 Port

          • P2 - Crashes, loss of data, severe memory leak.
          • Resolved
          links to

          Commit Commit openjdk/jdk11u/3a0074c0

          Review Review openjdk/jdk11u/31

          Activity

            People

              mdoerr Martin Doerr
              mdoerr Martin Doerr
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: