Return-Path: Delivered-To: apmail-harmony-commits-archive@www.apache.org Received: (qmail 82586 invoked from network); 8 Feb 2007 13:36:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Feb 2007 13:36:28 -0000 Received: (qmail 35707 invoked by uid 500); 8 Feb 2007 13:36:35 -0000 Delivered-To: apmail-harmony-commits-archive@harmony.apache.org Received: (qmail 35612 invoked by uid 500); 8 Feb 2007 13:36:34 -0000 Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list commits@harmony.apache.org Received: (qmail 35537 invoked by uid 99); 8 Feb 2007 13:36:34 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Feb 2007 05:36:34 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Feb 2007 05:36:26 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 1D0B6410959 for ; Thu, 8 Feb 2007 05:36:06 -0800 (PST) Message-ID: <24053872.1170941766116.JavaMail.jira@brutus> Date: Thu, 8 Feb 2007 05:36:06 -0800 (PST) From: "Vladimir Beliaev (JIRA)" To: commits@harmony.apache.org Subject: [jira] Commented: (HARMONY-2692) [drlvm][jit] throwing exception in mixed mode leaks memory In-Reply-To: <25359430.1166101461145.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HARMONY-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471329 ] Vladimir Beliaev commented on HARMONY-2692: ------------------------------------------- Next set of comment which may be helpfull. 1. obvious, still... To investigate the leak please modify attached ExceptionLeakTest.java to reduce number of iterations from 12'345'678 to 500'001 - so the program under memcheck will ends much faster... 2. I've run valgrind --leak-check=full ExceptionLeakTest and got the most heavy leak: ==15344== 23,509,056 (23,508,960 direct, 96 indirect) bytes in 489,770 blocks are definitely lost in loss record 55 of 55 ==15344== at 0x401B82E: malloc (vg_replace_malloc.c:149) ==15344== by 0x4C8B992: oh_add_new_handles(ObjectHandlesNew**) (object_handles.cpp:279) ==15344== by 0x4C8BA62: oh_allocate_handle(ObjectHandles**) (object_handles.cpp:300) ==15344== by 0x4C8BDCC: oh_allocate_local_handle() (object_handles.cpp:384) ==15344== by 0x4C1CF2D: class_alloc_new_object_and_run_constructor(Class*, Method*, unsigned char*) (jit_runtime_support.cpp:2077) ==15344== by 0x4C0353D: create_lazy_exception(Class*, Method*, unsigned char*, jvalue*) (exceptions_jit.cpp:151) ==15344== by 0x4C03B41: exn_propagate_exception(StackIterator*, ManagedObject**, Class*, Method*, unsigned char*, jvalue*) (exceptions_jit.cpp:313) ==15344== by 0x4C03F86: exn_throw_for_JIT(ManagedObject*, Class*, Method*, unsigned char*, jvalue*) (exceptions_jit.cpp:439) ==15344== by 0x4C0401C: exn_athrow(ManagedObject*, Class*, Method*, unsigned char*) (exceptions_jit.cpp:462) ==15344== by 0x4C044A5: rth_throw_lazy(Method*) (exceptions_jit.cpp:594) ==15344== by 0x4441BD4: ??? ==15344== by 0x8D6E203: ??? Thanks Vladimir > [drlvm][jit] throwing exception in mixed mode leaks memory > ---------------------------------------------------------- > > Key: HARMONY-2692 > URL: https://issues.apache.org/jira/browse/HARMONY-2692 > Project: Harmony > Issue Type: Bug > Components: DRLVM > Environment: Windows XP i686 > Reporter: Salikh Zakirov > Attachments: BufferWrap.java, ExceptionLeakTest.java > > > The function wrap() of nio buffers leaks memory when invoked with illegal arguments. > When the attached test BufferWrap.java is run on DRLVM, it steadily increases used memory until crash. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.