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

JVM carsh only with java_g in 1.3.1_09 for CaffeineMark3.0

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • P4
    • None
    • 1.3.1_09
    • hotspot
    • x86
    • windows_2000

    Description

      The licensee found a crash only when they use "java_g" for CaffeineMark3.0.
      The crash does not occur with "java".


      1. Reproducing Process

      The follwoings show the results in c1 and c2 for CaffeineMark3.0

      1.1 Client compiler(default)
       
      H:\Tools\cm30>w:\jdk1.3.1\bin\java_g -showversion CaffeineMarkEmbeddedApp
      java version "1.3.1_09"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_09-b01)
      Java HotSpot(TM) Client VM (build 1.3.1_09-b01-debug, mixed mode)

      Sieve score = 7705 (98)
      Loop score = 24515 (2017)
      Logic score = 17785 (0)
      String score = 19304 (708)
      Float score = 26477 (185)
      Method score = 18944 (166650)
      Overall score = 17866
       Locks owned:
      Mutex: [0x284770] Threads_lock - lock_count: 0
      #
      # HotSpot Virtual Machine Error, Internal Error
      # Please report this error at
      # http://java.sun.com/cgi-bin/bugreport.cgi
      #
      # Fatal: acquiring lock Terminator_lock/5 out of order with (at least) Threads_lock/4 -- possible
      dadlock
      #
      # Error ID: D:\BUILD_AREA\jdk131-update\ws\hotspot\src\share\vm\runtime\mutex.cpp, 155
      #
      # Problematic Thread: prio=5 tid=0x93d068 nid=0x778 runnable
      #
       
       
      1.2 Server compiler
       
      H:\Tools\cm30>w:\jdk1.3.1\bin\java_g -server -showversion CaffeineMarkEmbeddedApp
      java version "1.3.1_09"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_09-b01)
      Java HotSpot(TM) Server VM (build 1.3.1_09-b01-debug, mixed mode)

      Sieve score = 15691 (98)
      Loop score = 81297 (2017)
      Logic score = 106956 (0)
      String score = 9084 (708)
      Float score = 28406 (185)
      Method score = 32558 (166650)
      Overall score = 32350
       Locks owned:
      Mutex: [0x284770] Threads_lock - lock_count: 0
      #
      # HotSpot Virtual Machine Error, Internal Error
      # Please report this error at
      # http://java.sun.com/cgi-bin/bugreport.cgi
      #
      # Fatal: acquiring lock Terminator_lock/5 out of order with (at least) Threads_lock/4 -- possible
      dadlock
      #
      # Error ID: D:\BUILD_AREA\jdk131-update\ws\hotspot\src\share\vm\runtime\mutex.cpp, 155
      #
      # Problematic Thread: prio=5 tid=0x9b10b8 nid=0x3b8 runnable
      #
       
       
       
      2. Configration

       - OS : Windows 2000 Server SP3(Japanese)
       - J2SE 1.3.1_09-b01( Sun's official binary for licensee)


      3. Note
        
         They consider this issue is related to 4805573.
         They remove the fix for 4805573 out of 1.3.1_09 source code
         and build binary.
         Then they tried CaffeineMark in the above modified binary.
         The crash does not occur even with "java_g" command.

      Attachments

        Issue Links

          Activity

            People

              myangsunw Mingyao Yang (Inactive)
              tbaba Tadayuki Baba (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: