You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@harmony.apache.org by "Li-Gang Wang (JIRA)" <ji...@apache.org> on 2007/04/12 17:22:32 UTC

[jira] Updated: (HARMONY-3637) [Native Ref Enqueue Thread Design]Fixing the bug that VM sometimes can not enqueue references as quickly as some tests expect

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

Li-Gang Wang updated HARMONY-3637:
----------------------------------

    Attachment: 01_native_sync_enqueue_references.patch

> [Native Ref Enqueue Thread Design]Fixing the bug that VM sometimes can not enqueue references as quickly as some tests expect
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-3637
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3637
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Win/Linux 32/64
>            Reporter: Li-Gang Wang
>         Attachments: 01_native_sync_enqueue_references.patch
>
>
> gc.PhantomReferenceTest and tests.api.java.lang.ref.ReferenceTest in classlib expect weak references are enqueued once System.runFinalization() is called. Although I think Java specification doesn't require this, I provide the solution for this in the patch.

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