You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Gregory Shimansky (JIRA)" <ji...@apache.org> on 2007/12/28 14:02:11 UTC

[jira] Closed: (HARMONY-4905) [drlvm][thread] Last thread event before stick in Join is incorrect

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

Gregory Shimansky closed HARMONY-4905.
--------------------------------------

    Resolution: Fixed
      Assignee: Gregory Shimansky

Ok closing the bug according to evaluation.

> [drlvm][thread] Last thread event before stick in Join is incorrect
> -------------------------------------------------------------------
>
>                 Key: HARMONY-4905
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4905
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Windows XP
>            Reporter: Alexander N. Alexeev
>            Assignee: Gregory Shimansky
>         Attachments: event_log.txt, pack.zip
>
>
> When one thread spawns another and joins it, waiting for its
> termination, it becomes blocked on monitor  (from last handled event
> JVMTI_EVENT_MONITOR_CONTENDED_ENTER for that thread before 'sleep") ,
> while in other VMs (Sun's, IBM's and BEA's) thread which calls "Join"
> starts waiting (last event is JVMTI_EVENT_MONITOR_WAIT before
> 'sleep"). Probably set of events depends on VM internals, but in
> common sense "waited" state is more suitable for thread which waits
> for other thread termination.
> Events sequence can be seen at attached event_log.txt, place in  trace where Join happens is marked. 

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