harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chunrong Lai (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-5684) [drlvm][memory] Native memory management and tuning
Date Wed, 20 Aug 2008 08:56:44 GMT

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

Chunrong Lai commented on HARMONY-5684:

 It is also noted that one can reproduce the error with 
C:\harmony.latest\trunk\working_classlib>ant -Dtest.jre.home=c:\harmony.latest\t
runk\working_vm\build\windows_x86_msvc_debug\deploy\jdk\jre -Dtest.case="org.apa
che.harmony.lang.management.MemoryPoolMXBeanImplTest" test
C:\harmony.latest\trunk\working_classlib>java -cp .;c:\harmony.latest\trunk\work
junit_3.8.2\junit.jar junit.textui.TestRunner org.apache.harmony.lang.management
while the error message is like 
  java.lang.ClassCastException at   org.apache.harmony.lang.management.DynamicMXBeanImpl.invokeMethod(DynamicMXBeanImpl.java:416)
at org.apache.harmony.lang.management.DynamicMXBeanImpl.getAttribute(DynamicMXBeanImpl.java:190)
at org.apache.harmony.lang.management.MemoryPoolMXBeanImplTest.testGetAttribute(MemoryPoolMXBeanImplTest.java:263)
at java.lang.reflect.VMReflection.invokeMethod(VMReflection.java)

 Anybody want to have a look in this issue? 

> [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
> - 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.

View raw message