Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <20312406.1170850746314.JavaMail.jira@brutus>
Date: Wed, 7 Feb 2007 04:19:06 -0800 (PST)
From: "Gregory Shimansky (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Assigned: (HARMONY-3002) [drlvm] Race condition in threading
 code leads to VM crash on SMP systems on HARMONY-2386
In-Reply-To: <22076356.1168727307561.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-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Shimansky reassigned HARMONY-3002:
------------------------------------------

    Assignee: Gregory Shimansky

> [drlvm] Race condition in threading code leads to VM crash on SMP systems on HARMONY-2386
> -----------------------------------------------------------------------------------------
>
>                 Key: HARMONY-3002
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3002
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Linux ia32, windows ia32
>            Reporter: Gregory Shimansky
>         Assigned To: Gregory Shimansky
>         Attachments: wait_safe_region_event-removed-incorrect-early-return-condition.patch
>
>
> I am not sure this is a class loader bug, but the crash happens on class loader code in class_initialize. When running the test in HARMONY-2386 many times in a loop it crashes after some time. The fat monitor which is used for synchronization in Class::initialize appears to be uninitialized or corrupted. It could be a thread manager bug or enumeration problem as well.

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