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

[TESTBUG] serviceability/tmtools/jstack/WaitNotifyThreadTest.java still fails when run with flag -Xcomp

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P4
    • Resolution: Not an Issue
    • Affects Version/s: None
    • Fix Version/s: 12
    • Component/s: core-svc
    • Labels:
      None
    • Subcomponent:
    • Resolved In Build:
      master

      Description

      This is still failing in tier4:

      Error: incorrect monitor info: locked, a java.lang.Object, 0x000000078653eeb0
      Expected: locked, a java.lang.Object, no object reference available

      Looks like the presence/absence of an address is contingent on other things ??

      "MyWaitingThread" #13 prio=5 os_prio=0 cpu=0.27ms elapsed=2.63s tid=0x00007f522c009000 nid=0x62d0 in Object.wait() [0x00007f526537d000]
         java.lang.Thread.State: WAITING (on object monitor)
      Thread: 0x00007f522c009000 [0x62d0] State: _at_safepoint _has_called_back 0 _at_poll_safepoint 0
         JavaThread state: _thread_blocked
      at java.lang.Object.wait(java.base@12-internal/Native Method)
      - waiting on <no object reference available>
      at java.lang.Object.wait(java.base@12-internal/Object.java:328)
      at WaitNotifyThreadTest$WaitThread.run(WaitNotifyThreadTest.java:80)
      - locked <0x000000078653eeb0> (a java.lang.Object)

      Or maybe there is a bug in the stack printing code thats printing the information?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                dholmes David Holmes
                Reporter:
                dholmes David Holmes
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: