The reliability testing was done on Build 77(Beta 2).

J2DBench crashes with java.lang.OutOfMemoryError on Sparc 9 after 1 hour.

The machine configuration where it was tested is as follows:
dnm-dtf-004 (Solaris Sparc 9 64bit, s81_43)

It fails with both Client and 64bit Server VM after 1 hour.

The reliability testing was done on B72 before on Sparc9 and it ran for 28hours after which it exited with the same java.lang.OutOfMemoryError.

J2DBench runs fine(for 36 hours) in all other platforms on Build 77. It ran fine on Sparc 8 with client VM. We are yet to run with server mode on Sparc 8.

The testcase is located at
/net/sqesvr/export/2d/Merlin_2d_ws/J2Bench

The report is located at:
/net/sqesvr/deployment5/testlog/merlin/b77/reliability/j2dbench/SunOS_dnm-dtf-004_reports/J2DBench_Loop_Report_1.4.0-beta2-b77_1001211928824.html

There was no stack trace and it came out with
java.lang.OutOfMemoryError.


###@###.### 2001-10-08

I ran J2DBench on B81 with -d64 flag and it failed again with java.lang.OutOfMemoryError.
The machine I tested was dnm-dtf-004
The test failed after around an hour.

The testsuite is located at /net/sqesvr/export/2d/Merlin_2d_ws/J2DBench
I did the foll. to run the testsuite.
setenv JAVA_HOME /net/sqesvr/export/st1/jdk14-beta/b81/solsparc
setenv JAVA_FLAG -d64
gnumake runtimer

The above command terminates the application after exactly 36 hours. But because of the above failure, it came out after an hour.
The testcase was running fine on client VM (32 bit) for around 4 hours after which I manually terminated the app.

###@###.### 2001-10-08



The bug is no longer reproduceable on Hopper (jdk1.4.1, b10)
Verified with both clientVM and serverVM

The bug most likely got fixed due to the fix for the foll. bug

4525841: RAS: (2D) should attempt to reduce or eliminate use of finalizers

###@###.### 2002-05-08