[jira] Updated: (HARMONY-3997) [drlvm][exception] Class unloading support in lazy stack creation.

["Rana Dasgupta (JIRA)" <ji...@apache.org>]

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

Rana Dasgupta updated HARMONY-3997:
-----------------------------------

    Attachment: test-plugin-unloading.zip

Attaching a simple version of the pluging test from issue 3845.
Overall between 3845 and 3997, the 3997 approach looks better IMHO. But the patch here has a bug.???

Though the StackClasses array in Throwable.java is set to null after resolution, the classes array is not being collected. So this prevents unloading of the class loader. Probably somewhere the serialized state of the exception is being stored( though transient )?

In this version of the test, the RI unloads the CL when storedexception is set to null, as it should. In DRLVM, the approach is better I think, we can unload after the exception has been reolved.



> [drlvm][exception] Class unloading support in lazy stack creation.
> ------------------------------------------------------------------
>
>                 Key: HARMONY-3997
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3997
>             Project: Harmony
>          Issue Type: New Feature
>          Components: DRLVM
>            Reporter: Pavel Afremov
>         Attachments: 0001-First-version-of-class-unloading-support-in-lazy-sta.patch, 0002-Fast-version-of-class-unloading-support-in-lazy-stac.patch, test-plugin-unloading.zip
>
>
> First version of class unloading support in lazy stack creation.
> This version prevents class unloading if there is any stored exception. In Throwable class implementation array of java.lang.Class was added. This array contains classes of each method on the stack.

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