harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "weldon washburn (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-2742) [drlvm] Memory leak in threading system.
Date Thu, 10 May 2007 04:45:15 GMT

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

weldon washburn updated HARMONY-2742:

    Attachment: second_design004.patch

This patch sets aside fixing the gc_force_gc() problems.  In specific, the GC/VM API probably
needs to be extended to support gc_force_gc(MAJOR).  Currently there is zero way to force
a major collection.  And, until a major collection occurs, its probably next to impossible
to determine which fat locks are still alive.

Another problem with gc_force_gc() is that the cunit test framework does not support a jthread.lib
calling gc_force_gc() api.  See dev@harmony mailing list for additional details.

> [drlvm] Memory leak in threading system.
> ----------------------------------------
>                 Key: HARMONY-2742
>                 URL: https://issues.apache.org/jira/browse/HARMONY-2742
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Pavel Afremov
>         Assigned To: weldon washburn
>         Attachments: ManyThreadsTest.java, release_fat_monitors_gcv4.1.patch, second_design001_gc_gen.diff,
second_design001_thread_manager.diff, second_design002.diff, second_design003.patch, second_design004.patch,
> Creating, starting and joining thread is source of memory leak. This leak is not fixed
by patch from HARMONY-2437.

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

View raw message