You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Tim Ellison (JIRA)" <ji...@apache.org> on 2007/10/23 13:12:50 UTC
[jira] Commented: (HARMONY-4014) [drlvm][thread]100% CPU
consumption in MONITORENTER
[ https://issues.apache.org/jira/browse/HARMONY-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536962 ]
Tim Ellison commented on HARMONY-4014:
--------------------------------------
Is this issue still valid given the latest thread changes? It is still listed as blocking a critical issue.
> [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
> Assignee: weldon washburn
> Priority: Minor
> Attachments: Test.java
>
>
> The attached 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.