Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <1868863135.1211862837914.JavaMail.jira@brutus>
Date: Mon, 26 May 2008 21:33:57 -0700 (PDT)
From: "Alexey Varlamov (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Commented: (HARMONY-5843) [drlvm][gc] class unloading is
 unstable
In-Reply-To: <411476244.1211782077057.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HARMONY-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599957#action_12599957 ] 

Alexey Varlamov commented on HARMONY-5843:
------------------------------------------

This is a suite for checking conformance to lazy class loading/resolution behaviour. Occasionally it puts a strain on CU facilities, thus I added the StressTest to reveal instabilities there.

> [drlvm][gc] class unloading is unstable
> ---------------------------------------
>
>                 Key: HARMONY-5843
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5843
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Alexey Varlamov
>            Assignee: Chunrong Lai
>
> On class-unloading scenarious, DRLVM easily hits a bunch of asserts in gc_gen. Most typical asserts are:
>     [junit] Assertion failed: obj && obj->vt_raw, file c:\users\avarlamo\trunk\working_vm\vm\gc_gen\src\common\gc_for_class.h, line 207
>     [junit] Assertion failed: address_belongs_to_gc_heap(addr, gc), file c:\users\avarlamo\trunk\working_vm\vm\gc_gen\src\thread\../gen/gen.h, line 152
>     [junit] Assertion failed: vm_object_size(obj) != 0, file c:\users\avarlamo\trunk\working_vm\vm\gc_gen\src\common\gc_block.h, line 146
> These asserts fire intermittently, may be reproduced in any mode including interpreter and on any platform (yet on different machines a particular assert happens more often than others).
> To reproduce, run lazy.test suite:
> working_vm$ ant lazy.test
> For convenience, there is standalone launcher org.apache.harmony.vm.test.lazyresolution.StressTest which can vary stress load, e.g.:
> working_vm$ cd build\windows_x86_msvc_debug\tests\lazy.tests\classes
> classes$ java -cp .;junit.jar -Dlazy.test.iterations=100 -Dlazy.test.threads=10 org.apache.harmony.vm.test.lazyresolution.StressTest

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.