[jira] Commented: (HARMONY-5241) [drlvm][jit][opt] Emitter provokes java objects creation

["Pavel Pervov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HARMONY-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547856 ] 

Pavel Pervov commented on HARMONY-5241:
---------------------------------------

The source is outside of encoder. There are many places in Jitrino, where object allocation happens during compilation.

The source is in IRManager::resolveRuntimeInfo.

Call chain is as follows:

IRManager::resolveRuntimeInfo (case Opnd::RuntimeInfo::Kind_StringAddress)
->CompilationInterface::loadStringObject
->class_get_const_string_intern_addr
->vm_instantiate_cp_string_resolved
->Global_Env::string_pool::intern
->string_create_from_utf8 & org/apache/harmony/kernel/vm/VM.intern

So, not only java/lang/String is created, but it is also added into WeakHashMap.

> [drlvm][jit][opt] Emitter provokes java objects creation
> --------------------------------------------------------
>
>                 Key: HARMONY-5241
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5241
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>         Environment: x86, x86_64
>            Reporter: Evgueni Brevnov
>
> While running stress.org.apache.harmony.test.stress.gc.frag.Fragmentation test I noted that emitter pass finishes with OutOfMemory excpetion raised (which was not handled in any way :-(). Investigation showed the reason is creation of j.l.String objects during runtime info resolution. I believe that proper solution should eliminate string objects creation at all. If it is not possible then we should properly handle OutOfMemory.
> Thanks
> Evgueni.

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