You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexey Varlamov (JIRA)" <ji...@apache.org> on 2008/02/08 12:46:08 UTC

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

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

Alexey Varlamov resolved HARMONY-5241.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.0M5

Applied the second patch  at revision: 619840

> [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
>            Assignee: Alexey Varlamov
>             Fix For: 5.0M5
>
>         Attachments: ld_ref.patch, ld_ref2.patch
>
>
> 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.