Return-Path: Delivered-To: apmail-incubator-harmony-commits-archive@www.apache.org Received: (qmail 34461 invoked from network); 30 Oct 2006 16:51:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Oct 2006 16:51:29 -0000 Received: (qmail 72201 invoked by uid 500); 30 Oct 2006 16:51:40 -0000 Delivered-To: apmail-incubator-harmony-commits-archive@incubator.apache.org Received: (qmail 72172 invoked by uid 500); 30 Oct 2006 16:51:40 -0000 Mailing-List: contact harmony-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: harmony-dev@incubator.apache.org Delivered-To: mailing list harmony-commits@incubator.apache.org Received: (qmail 72159 invoked by uid 99); 30 Oct 2006 16:51:40 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Oct 2006 08:51:40 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Oct 2006 08:51:26 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 741977142D7 for ; Mon, 30 Oct 2006 08:50:18 -0800 (PST) Message-ID: <1124131.1162227018472.JavaMail.root@brutus> Date: Mon, 30 Oct 2006 08:50:18 -0800 (PST) From: "Pavel Pervov (JIRA)" To: harmony-commits@incubator.apache.org Subject: [jira] Commented: (HARMONY-1833) [DRLVM] deadlock during finalization In-Reply-To: <12947644.1160628936705.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ http://issues.apache.org/jira/browse/HARMONY-1833?page=comments#action_12445649 ] Pavel Pervov commented on HARMONY-1833: --------------------------------------- Now the patch is ok. Still, to my thinking, malloc'ing small local blocks is not a good practice. > [DRLVM] deadlock during finalization > ------------------------------------ > > Key: HARMONY-1833 > URL: http://issues.apache.org/jira/browse/HARMONY-1833 > Project: Harmony > Issue Type: Bug > Components: DRLVM > Environment: SLES 9 32-bit SP2; CPU 2xXeon x64 > gcc 3.3.3 drlvm debug build > Reporter: Alexey Varlamov > Attachments: H-1833.patch, H-1833.patch > > > The classlib tests hang sporadically, usually in JNDI module when running all classlib unit tests (single runs of JNDI alone always ok). > Investigation shows that there are deadlocks happening between main thread (MT) and finalizer thread (FT): > 1) MT performs classloading, it grabs ClassLoader::_lock; > 2) GC happens, FinalizerThread.startFinalization() is called, FT activates; > 3) FT invokes some finalize() method, compilation starts and grabs g_compileLock; > 4) FT waits for ClassLoader::_lock to allocate code_chunk_info; > 5) MT proceeds to compilation of FinalizerThread.spawnBalanceThreads() and waits for g_compileLock; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira