[jira] Updated: (HARMONY-5822) [drlvm][vmcore] class unloading does not clean JIT recompilation callbacks

["Alexey Varlamov (JIRA)" <ji...@apache.org>]

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

Alexey Varlamov updated HARMONY-5822:
-------------------------------------

    Attachment: HARMONY-5822.patch

To reproduce, run lazy-resolution suite (HARMONY-3874) in server mode.

A dirty POC fix allowing to pass the suite, not for committing. 
Better fix should add an extra cycle iterating on classloaders being unloaded to unregister all callback before dismissing native data.

And ideally all this recompilation stuff should move to EM. 
BTW EM profiles are not unloaded either and may cause crashes if recompilation is triggered concurrently with unloading.

> [drlvm][vmcore] class unloading does not clean JIT recompilation callbacks
> --------------------------------------------------------------------------
>
>                 Key: HARMONY-5822
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5822
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>    Affects Versions: 5.0M6
>            Reporter: Alexey Varlamov
>         Attachments: HARMONY-5822.patch
>
>
> There is a facility in DRLVM for notifying JIT of method recompilation, see vm_register_jit_recompiled_method_callback(JIT_Handle jit, Method_Handle method, void *callback_data).
> Jitrino uses this feature to patch direct calls to methods (within other compiled methods) upon recompilation of a callee method.
> However, in case then a caller method is unloaded, corresponding callbacks are not removed and lead to SIGSEGV if a callee method is recompiled.

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