[jira] Commented: (HARMONY-3148) [Classlib][nio] alloc many DirectByteBuffers may cause memory-out-error

["Jimmy, Jing Lv (JIRA)" <ji...@apache.org>]

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

Jimmy, Jing Lv commented on HARMONY-3148:
-----------------------------------------

    Solution for this issue is still in discussing, one good thought is modify current GC to handle native memory as Java heap, but this may be a long way to go to reach this target.
    A quick solution is detect native memory usage in classlib native code, and call System.gc() if necessary.

> [Classlib][nio] alloc many DirectByteBuffers may cause memory-out-error
> -----------------------------------------------------------------------
>
>                 Key: HARMONY-3148
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3148
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>            Reporter: Jimmy, Jing Lv
>
> Hi,
>      As discussed on mailing-list, DirectByteBuffer uses native memory which is out of GC-control, alloc many DirectByteBuffer may cause memory-out-error if they are not GCed, even they can be GCed at that time. 
>      This happens in Harmony but not in RI. This should be a bug of Harmony.
>      Note: other native memory users, e.g., java.util.zip.Deflater, may cause this problem as well.

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