You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Vera Petrashkova (JIRA)" <ji...@apache.org> on 2007/07/11 07:06:04 UTC
[jira] Created: (HARMONY-4413) [buildtest][reliability] Reliability
test vm.finalization.ArrayElemFinalizationTest fails with OOME
[buildtest][reliability] Reliability test vm.finalization.ArrayElemFinalizationTest fails with OOME
---------------------------------------------------------------------------------------------------
Key: HARMONY-4413
URL: https://issues.apache.org/jira/browse/HARMONY-4413
Project: Harmony
Issue Type: Bug
Components: build - test - ci
Reporter: Vera Petrashkova
Priority: Minor
The following Reliability test
creates 2 arrays of 1000 Objects. To assign each of these elements the test additionally creates array of 1000 bytes.
Then it starts 100 threads and tries to modify elements of created arrays.
As the result this test creates a lot of arrays but it does not define the VM behavior in case of OutOfMemoryError.
When this test runs on RI or on BEA JRockit VM reports sometimes OutOfMemoryError, for example,
Exception in thread "Thread-130403" java.lang.OutOfMemoryError: Java heap space
In this case the test execution is continued but sometimes it fails.
It looks like OOME is the reason of intermittent failures of this test on Harmony.
This test should be fixed. There are 2 ways:
1) Define the values of the fields N_OF_THREADS, ARRAY_SIZE, BYTE_ARRAY_SIZE using test parameters.
The source code of the test contains empty method parseParams.
It is needed to define fields initialization in this method and starts test with appropriate arguments,
for example, number of threads = 50, object array size = 100 and byte array size = 1000.
2) To define the test behavior in case of OutOfMemoryError.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.