Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <24231150.1195228243043.JavaMail.jira@brutus>
Date: Fri, 16 Nov 2007 07:50:43 -0800 (PST)
From: "Pavel Rebriy (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Updated: (HARMONY-5135) DRL VM hangs during stress.Mix
 running on x86-64
In-Reply-To: <24737039.1195226623109.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-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Rebriy updated HARMONY-5135:
----------------------------------

    Attachment: lock_table_fix.patch

The patch which eliminates safe point from locktable_write_enter and locktable_read_enter.

> DRL VM hangs during stress.Mix running on x86-64
> ------------------------------------------------
>
>                 Key: HARMONY-5135
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5135
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Linux x86-64
>            Reporter: Pavel Afremov
>         Attachments: lock_table_fix.patch
>
>
> The safe_point called from hycond_wait, which called from many places include locktable_reader_enter and locktable_writer_enter.
> From other side access to locatable there is in function hythread_reclaim_recources, which works during stop the world. 
> It leads to dead lock, when first thread, which catch locktable monitor goes into safe poin and GC starts. In this case GC can't complete work, because one or several threads waiting on following stack, when first thread free locktable monitor:
> 	#1 <pthread_mutex_lock>
> 	#2 <hymutex_lock>
> #3<hythread_reclaim_resources>
> #4 <vm_reclaim_native_objs>
> #5 <gc_reclaim_heap>
> #6 <fspace_alloc>
> #7 ....
> So it's a deadlock when firs thread waits when second thread free monitor, and send thread waits when first thread free the other monitor.

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