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/10 17:28:43 UTC

[jira] Updated: (HARMONY-5287) [drlvm][jvmti] Lack of synchronization in GetLoadedClasses and GetClassLoaderClasses may cause VM to crash

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

Gregory Shimansky updated HARMONY-5287:
---------------------------------------

    Attachment: patch

Patch that adds synchronization.

> [drlvm][jvmti] Lack of synchronization in GetLoadedClasses and GetClassLoaderClasses may cause VM to crash
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-5287
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5287
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>    Affects Versions: 5.0M4
>            Reporter: Gregory Shimansky
>            Assignee: Gregory Shimansky
>            Priority: Critical
>             Fix For: 5.0M4
>
>         Attachments: patch
>
>
> Recent runs of jdktools show unstable tests that sometimes crash in GetLoadedClasses function. The reason is that the number of reported classes from classloader tables is bigger than memory allocated for them. It happens because some classes may be loaded between the count of loaded classes it known and filling up the reported array. In debug mode assertion "number == count" often fails for this reason ("count" is the number of classes determined for allocating memory, "number" is the number of actually reported classes).
> Attached patch adds synchronization to these functions. Tests work stably for me now. I would really like to commit this fix in M4, so marking this bug as M4.

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