harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene S. Ostrovsky (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-3972) [drlvm][thread] hardcoded limit for monitors owned by a thread
Date Fri, 15 Jun 2007 08:13:26 GMT

     [ https://issues.apache.org/jira/browse/HARMONY-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eugene S. Ostrovsky updated HARMONY-3972:
-----------------------------------------

    Attachment: H3972-Dynamic-monitors-array-reallocation.patch

Added patch:
  H3972-Dynamic-monitors-array-reallocation.patch

Fix for the issue.

> [drlvm][thread] hardcoded limit for monitors owned by a thread
> --------------------------------------------------------------
>
>                 Key: HARMONY-3972
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3972
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Eugene S. Ostrovsky
>         Attachments: H3972-Dynamic-monitors-array-reallocation.patch, H3972-Regression-test.patch
>
>
> VM with enabled jvmti has hardcoded limit for monitors owned by a thread.
> thread_private.h:
> .....
> #define MAX_OWNED_MONITOR_NUMBER 200 //FIXME: switch to dynamic resize
> .....
> thread_java_monitors.c
> .....
>     assert(tm_java_thread->owned_monitors_nmb < MAX_OWNED_MONITOR_NUMBER);
> .....
> Thus exceeding 200 owned monitors we will get assertion on  debug configuration and unpredicted
behavior on release..

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


Mime
View raw message