From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22518 invoked by alias); 5 Apr 2011 12:55:19 -0000 Received: (qmail 22507 invoked by uid 22791); 5 Apr 2011 12:55:18 -0000 X-SWARE-Spam-Status: No, hits=-6.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 05 Apr 2011 12:55:11 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p35Ct9rd003672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 5 Apr 2011 08:55:09 -0400 Received: from zebedee.pink (ovpn-113-109.phx2.redhat.com [10.3.113.109]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p35Ct7dl012781; Tue, 5 Apr 2011 08:55:08 -0400 Message-ID: <4D9B112B.6000408@redhat.com> Date: Tue, 05 Apr 2011 12:55:00 -0000 From: Andrew Haley User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Thunderbird/3.1.9 MIME-Version: 1.0 To: Erik Groeneveld CC: java@gcc.gnu.org Subject: Re: GC leaks debugging References: <4D95909E.4060309@redhat.com> <4D959C24.8030408@redhat.com> <238A96A773B3934685A7269CC8A8D04272EFEFD5C3@GVW0436EXB.americas.hpqcorp.net> <4D997D8C.9060903@redhat.com> <4D9993D4.9040704@redhat.com> <4D9ADA89.8000307@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact java-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-owner@gcc.gnu.org X-SW-Source: 2011-04/txt/msg00030.txt.bz2 On 04/05/2011 01:02 PM, Erik Groeneveld wrote: >>> >>> I have done many tests, with different programs, which all run >>> flawlessly on OpenJDK, but explode on GCJ. I have run some test last >>> night, and I'll see from the logs that the heap is 1 GB, while about >>> 700 MB of it is free. >> >> That sounds like it's working perfectly, then. What is the problem? > > The problem is that the tests don't use much memory at all, but the > heap keeps expanding, the collection cycles become less frequent and > take longer and longer. Even on a system with 64GB, it just fills it > up. > > The tests work fine on OpenJDK. What could cause GCJ to grow the heap > infinitely? I don't know because you won't show me the tests. Andrew.