You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Eugene S. Ostrovsky (JIRA)" <ji...@apache.org> on 2007/05/25 10:57:16 UTC
[jira] Created: (HARMONY-3972) [drlvm][thread] hardcoded limit for
monitors owned by a thread
[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
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.
[jira] Commented: (HARMONY-3972) [drlvm][thread] hardcoded limit
for monitors owned by a thread
Posted by "Pavel Rebriy (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HARMONY-3972) [drlvm][thread] hardcoded limit for
monitors owned by a thread
Posted by "Eugene S. Ostrovsky (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HARMONY-3972) [drlvm][thread] hardcoded limit for
monitors owned by a thread
Posted by "Ilya Berezhniuk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya Berezhniuk updated HARMONY-3972:
-------------------------------------
Attachment: H3972-Dynamic-monitors-array-reallocation.patch
Reattaching with license granted.
> [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
> Assignee: weldon washburn
> Priority: Minor
> Attachments: H3972-Dynamic-monitors-array-reallocation.patch, H3972-Dynamic-monitors-array-reallocation.patch, 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.
[jira] Closed: (HARMONY-3972) [drlvm][thread] hardcoded limit for
monitors owned by a thread
Posted by "weldon washburn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
weldon washburn closed HARMONY-3972.
------------------------------------
Resolution: Fixed
patch has been applied
> [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
> Assignee: weldon washburn
> Priority: Minor
> Attachments: H3972-Dynamic-monitors-array-reallocation.patch, H3972-Dynamic-monitors-array-reallocation.patch, 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.
[jira] Updated: (HARMONY-3972) [drlvm][thread] hardcoded limit for
monitors owned by a thread
Posted by "Ilya Berezhniuk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya Berezhniuk updated HARMONY-3972:
-------------------------------------
Attachment: H3972-Dynamic-monitors-array-reallocation.patch
Attaching patch updated according thread manager changes.
Regression test should work without changes.
> [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
> Assignee: weldon washburn
> Priority: Minor
> Attachments: H3972-Dynamic-monitors-array-reallocation.patch, 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.
[jira] Updated: (HARMONY-3972) [drlvm][thread] hardcoded limit for
monitors owned by a thread
Posted by "weldon washburn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
weldon washburn updated HARMONY-3972:
-------------------------------------
Priority: Minor (was: Major)
> [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
> Assignee: weldon washburn
> Priority: Minor
> 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.
[jira] Updated: (HARMONY-3972) [drlvm][thread] hardcoded limit for
monitors owned by a thread
Posted by "Eugene S. Ostrovsky (JIRA)" <ji...@apache.org>.
[ 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-Regression-test.patch
Added file:
H3972-Regression-test.patch
Regression test 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-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.
[jira] Assigned: (HARMONY-3972) [drlvm][thread] hardcoded limit for
monitors owned by a thread
Posted by "weldon washburn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
weldon washburn reassigned HARMONY-3972:
----------------------------------------
Assignee: weldon washburn
> [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
> Assignee: weldon washburn
> 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.