From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16151 invoked by alias); 22 Jun 2004 16:56:34 -0000 Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org Received: (qmail 16134 invoked by uid 48); 22 Jun 2004 16:56:33 -0000 Date: Tue, 22 Jun 2004 17:21:00 -0000 Message-ID: <20040622165633.16133.qmail@sourceware.org> From: "mckinlay at redhat dot com" To: java-prs@gcc.gnu.org In-Reply-To: <20040622101536.16134.hannes@helma.at> References: <20040622101536.16134.hannes@helma.at> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libgcj/16134] Memory leak in String.getBytes() X-Bugzilla-Reason: CC X-SW-Source: 2004-q2/txt/msg00249.txt.bz2 List-Id: ------- Additional Comments From mckinlay at redhat dot com 2004-06-22 16:56 ------- There is certainly a problem with the encoder cache here in that cache lookups will always fail. I've written the obvious patch and will check it in shortly. However the leak you see is not due to this code directly because it never keeps more than 4 encoder instances in the cache. Rather, it is due to the stack-walking code leaking memory as part of the calling classloader check in Class.forName(). This was fixed in gcc 3.4, see bug 12475. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16134