From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10570 invoked by alias); 5 Apr 2011 09:02:10 -0000 Received: (qmail 10560 invoked by uid 22791); 5 Apr 2011 09:02:09 -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 09:02:04 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p35923fD024342 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 5 Apr 2011 05:02:03 -0400 Received: from zebedee.pink (ovpn-113-109.phx2.redhat.com [10.3.113.109]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p35921Q9004800; Tue, 5 Apr 2011 05:02:02 -0400 Message-ID: <4D9ADA89.8000307@redhat.com> Date: Tue, 05 Apr 2011 09:02: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> 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/msg00028.txt.bz2 On 05/04/11 07:49, Erik Groeneveld wrote: > [...] >>> Any real program produces so much blacklist messages that it hardly >>> runs. I'd like to investigate this or am I on the wrong track >>> completely? >> >> I think you are. The heap is small in this simple test case, so there >> are no real problems. > > I will ignore this for now then. > >> You need to find out what the real problem is. Find just one of those >> "need to allocate large block" messages, and find out why it is being >> called. I suspect that there is an actual bug that is causing the >> explosion and it can be found. Forget about 991 blacklist messages: >> not useful. > > 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? > Also it seems that the finalization table keeps growing. I am > running now, but later this day I'll post the log. (And search the > mail archives with a new keyword: finalization ;-) There is a known problem with finalization and weak references, but I don't know the details. Maybe someone else can remeber. >> I'd have a look myself, but there is no way to duplicate your problem. >> BTW, is this on a 32-bit or 64-bit platform? > > It is on 32-bit. On 64 bit, the blacklisting is not happening. But > the heap keeps exploding, so you are right, the problem probably lies > elsewhere. OK, so you can concentrate on the 64-bit system, and forget about all the blacklisting noise. Andrew.