You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Salikh Zakirov (JIRA)" <ji...@apache.org> on 2006/10/24 17:12:21 UTC
[jira] Created: (HARMONY-1952) [drlvm] do not call any java from
vm_hint_finalize()
[drlvm] do not call any java from vm_hint_finalize()
----------------------------------------------------
Key: HARMONY-1952
URL: http://issues.apache.org/jira/browse/HARMONY-1952
Project: Harmony
Issue Type: Bug
Reporter: Salikh Zakirov
Currently, the finalization subsystem uses notification methods vm_hint_finalize(), which
is run by GC from arbitary allocation points. It can cause spurious ClassCircularityError.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HARMONY-1952) [drlvm] do not call any java from
vm_hint_finalize()
Posted by "Salikh Zakirov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-1952?page=all ]
Salikh Zakirov updated HARMONY-1952:
------------------------------------
Attachment: no-java-in-vm-hint-finalize.diff
no-java-in-vm-hint-finalize.diff is a RFC (request for comments) on how this could be achieved. It replaces running java method from vm_hint_finalize() by notifying on finalizer thread class.
It also changes finalizer thread to use the same object for synchronization.
The patch compiles and seems to run smoke tests on Windows/ia32 okay.
*RFC* Please review and comment. Please do not commit.
> [drlvm] do not call any java from vm_hint_finalize()
> ----------------------------------------------------
>
> Key: HARMONY-1952
> URL: http://issues.apache.org/jira/browse/HARMONY-1952
> Project: Harmony
> Issue Type: Bug
> Reporter: Salikh Zakirov
> Attachments: no-java-in-vm-hint-finalize.diff
>
>
> Currently, the finalization subsystem uses notification methods vm_hint_finalize(), which
> is run by GC from arbitary allocation points. It can cause spurious ClassCircularityError.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira