JDK-6648715 : assert(false,"Non-balanced monitor enter/exit!")
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 7
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2008-01-09
  • Updated: 2012-02-01
  • Resolved: 2009-03-26
Related Reports
Duplicate :  
JDK-6699669 - Hotspot server leaves synchronized block with monitor in bad state
Relates :  
JDK-6862370 - c1 assert(false,"Non-balanced monitor enter/exit!") with -XX:-UseFastLocking -Xcomp
Description
Here is an entry from my nightly analysis report:

New JDI_REGRESSION failures (from 2007.08.23)
    com/sun/jdi/ExceptionEvents.java
        This test failed the following assertion:

            Internal Error (src/share/vm/runtime/synchronizer.cpp:3432)
            Error: assert(false,"Non-balanced monitor enter/exit!")

        on Solaris SPARC Client VM (machine nanonano). I found the
        following bug that names this assertion:

            6302798 2/2 Java2Demo assertion failure with biased locking

        However, this bug was fixed way back in Mustang-B46.

        ###@###.### sent an e-mail reporting a sighting
        of this assertion on 2006.07.31. There was reply from Ken
        asking for more details, but I have no further e-mails.

The above entry was with Dolphin-B18 JDK bits, but with a newer VM
so this is a Dolphin-B19ish failure.
Comments
EVALUATION This bug might be the same as 6699669. The root cause of the problem is that the _owner field of the ObjectMonitor might point to an address during OSR transition and that address might become invalid later due to the frame shrinking.
26-03-2009