harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Rebriy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-3972) [drlvm][thread] hardcoded limit for monitors owned by a thread
Date Fri, 20 Jul 2007 06:39:06 GMT

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

Pavel Rebriy commented on HARMONY-3972:
---------------------------------------

The patch should be updated after commit HARMONY-3985 commit.

> [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