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

VM crash with heavy loading test program in 1.3.1_06

    XMLWordPrintable

    Details

    • Subcomponent:
    • Resolved In Build:
      10
    • CPU:
      sparc
    • OS:
      solaris_8

      Description

      When user tested 1.3.1_06 with the attached program on Solaris Box,
      VM crashed.

      1. Reproduce

       1) Compile the attached program.(X.java)
       2) Launch the command line,
            java -Xms384m -Xmx384m X

       3) You will see the list in display.
          Please see the last line.
          Segmentation fault occurs ( No dump(core) file appear.)

      ===>
      jle[15]% java -Xms384m -Xmx384m X
      1% passage...
      2% passage...
      3% passage...
      4% passage...
      5% passage...

      .......

      96% passage...
      97% passage...
      98% passage...
      99% passage...
       compute time : 37128 [ms]
      compute count : 10000 [turn/th]
           multiple : 100 [threds]
            threads : 1000 [threds]
      Segmentation Fault
      <===
        

      2. Configration

           OS : SunOS jle 5.8 Generic_108528-18 sun4u sparc SUNW,Ultra-80
           Memory : 2048 Megabytes
           MPU : UltraSPARC-II 450[MHz] *2 (dual)
           JRE/JDK :
      java version "1.3.1_06"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01)
      Java HotSpot(TM) Client VM (build 1.3.1_06-b01, mixed mode)


      3. Note

       - I did not try to reproduce windows and linux because
         my machines have less memory and I couldn't execute the command.
         User tried this on Solaris/Windows/Linux and the crash happened to
         all of them.
         
         Solaris: Solaris7, Sparc64 III 296MHz x 2, 2Gbyte
            Crash with the above mentioned message.

         Windows: Windows2000, Pentium III Xeon 700MHz x 4, 1.5Gbyte
            Crash with
               "Another exception has been detected while we were
                handling last error. Dumping information about last error:"
             or
               "Another exception has been detected while we were
                handling last error."

         Linux : RedHat 2.1(Advanced Server), Pentium III Xeon 700MHz x 4, 3.5Gbyte
          Crash with
           "Another exception has been detected while we were handling last error.
             Dumping information about last error:
             ERROR REPORT FILE = (N/A)
             PC = 0x0x415e5641
             SIGNAL = 11
             FUNCTION NAME = (N/A)
             LIBRARY NAME = (N/A)
             Please check ERROR REPORT FILE for further information, if there is any.
             Good bye."

       - This crash seems to occur on multi processor system.
       - This does not happen to 1.4.2-beta-b13 and build 1.4.1_01-b01.
      ============================================================================

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: