Return-Path: Delivered-To: apmail-harmony-commits-archive@www.apache.org Received: (qmail 19754 invoked from network); 31 May 2007 13:54:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 May 2007 13:54:36 -0000 Received: (qmail 70510 invoked by uid 500); 31 May 2007 13:54:40 -0000 Delivered-To: apmail-harmony-commits-archive@harmony.apache.org Received: (qmail 70495 invoked by uid 500); 31 May 2007 13:54:40 -0000 Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list commits@harmony.apache.org Received: (qmail 70486 invoked by uid 99); 31 May 2007 13:54:40 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 May 2007 06:54:40 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED 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; Thu, 31 May 2007 06:54:36 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id BE05C714180 for ; Thu, 31 May 2007 06:54:15 -0700 (PDT) Message-ID: <18447476.1180619655775.JavaMail.jira@brutus> Date: Thu, 31 May 2007 06:54:15 -0700 (PDT) From: "Sergey Salishev (JIRA)" To: commits@harmony.apache.org Subject: [jira] Created: (HARMONY-4014) [drlvm][thread]100% CPU consumption in MONITORENTER MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [drlvm][thread]100% CPU consumption in MONITORENTER --------------------------------------------------- Key: HARMONY-4014 URL: https://issues.apache.org/jira/browse/HARMONY-4014 Project: Harmony Issue Type: Bug Components: DRLVM Reporter: Sergey Salishev The attache test eats 100% of cpu time on Harmony while on RI it's 0% as it's blocked in IO op. This is caused by busy wait in monitor enter when trying to inflate thin lock which is held by thread blocked in OS from other thread. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.