[jira] Commented: (HARMONY-5684) [drlvm][memory] Native memory management and tuning

["Chunrong Lai (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HARMONY-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619040#action_12619040 ] 

Chunrong Lai commented on HARMONY-5684:
---------------------------------------


 I can see the commit breaks the org.apache.harmony.lang.management.MemoryPoolMXBeanImplTest and org.apache.harmony.lang.management.tests.java.lang.management.MemoryPoolMXBeanTest from classlib test suite. Any idea about that?

> [drlvm][memory] Native memory management and tuning
> ---------------------------------------------------
>
>                 Key: HARMONY-5684
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5684
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>            Reporter: Andrey Yakushev
>            Assignee: Pavel Pervov
>         Attachments: memmgr.patch, memmgr.patch
>
>
> There are several problems in DRLVM with native memory usage. For example:
> - Native memory usage couldn't be monitored currently in details via java.lang.management functionality
> - No explicit way to replace system native memory allocator to other memory managers in order to improve performance or footprint
> - Too many variants of the native memory allocations in DRLVM
> - Poor memory usage control (like leaks, double free calling, etc.)
> - Potential crash in diagnostics when OutOfMemory occur
> - Frequent native memory usage could cause OutOfMemory if GC wouldn't be timely called
> - No detail trace for the native memory usage
> Adding of some functionality to solve these would be hepful I think?

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