From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id 3FFDBBC57 for ; Wed, 18 Aug 2010 14:22:36 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiMCAL9ta0zZSMDjkWdsb2JhbACgShUBAQEBCQsKBxEDH78EhTcE X-IronPort-AV: E=Sophos;i="4.56,227,1280700000"; d="scan'208";a="67935897" Received: from fmmailgate02.web.de ([217.72.192.227]) by mail4-smtp-sop.national.inria.fr with ESMTP; 18 Aug 2010 14:22:24 +0200 Received: from smtp03.web.de ( [172.20.0.65]) by fmmailgate02.web.de (Postfix) with ESMTP id 960EA16E431FF; Wed, 18 Aug 2010 14:22:23 +0200 (CEST) Received: from [78.43.204.177] (helo=frosties.localdomain) by smtp03.web.de with asmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.110 #24) id 1Olhex-0006t7-00; Wed, 18 Aug 2010 14:22:23 +0200 Received: from mrvn by frosties.localdomain with local (Exim 4.72) (envelope-from ) id 1Olhex-0006dC-0o; Wed, 18 Aug 2010 14:22:23 +0200 From: Goswin von Brederlow To: Paul Steckler Cc: caml-list@yquem.inria.fr Subject: Re: [Caml-list] More re GC hanging References: Date: Wed, 18 Aug 2010 14:22:22 +0200 In-Reply-To: (Paul Steckler's message of "Sun, 15 Aug 2010 15:57:08 +1000") Message-ID: <87sk2ccdq9.fsf@frosties.localdomain> User-Agent: Gnus/5.110009 (No Gnus v0.9) XEmacs/21.4.22 (linux, no MULE) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: goswin-v-b@web.de X-Sender: goswin-v-b@web.de X-Provags-ID: V01U2FsdGVkX18arX63uGw3/PxkFsDN5oaWDuFbwg8HrUctVH3Z +Nk+1mEuJDhfqxZMq7TZJFVFlHdr+jhKG6N/42bFh4wVQjlYPH +AxDINq7Y= X-Spam: no; 0.00; steckler:01 steck:01 verbose:01 computed:01 12.:98 mfg:98 garbage:01 integer:01 heap:01 heap:01 caml-list:01 minor:01 minor:01 writes:01 hangs:01 Paul Steckler writes: > I haven't yet come up with a solution to the GC hanging problem I > mentioned the other day. > > But here's something that looks funny. I changed the default minor > heap size, the major > heap increment, the allocation policy. I also threw in a > `Gc.major_slice 0' in the code. > After turning on the Gc verbose option, I see: > > New heap increment size: 1000k bytes > New allocation policy: 1 > New minor heap size: 500k bytes > <>Starting new major GC cycle > allocated_words = 9404 > extra_heap_resources = 49000u > amount of work to do = 249956u > ordered work = 0 words > computed work = 44081 words > Marking 44081 words > Subphase = 10 > !<>Sweeping 9223372036854775807 words > Starting new major GC cycle > Marking 9223372036854775807 words > Subphase = 10 > Sweeping 9223372036854775807 words > > Those are some big mark and sweep numbers at the end! > > I'm using the x64 version of Fedora 12. Maybe the 64-bit garbage > collector has some integer > overflow problems? > > I wasn't seeing those huge numbers in other experiments where the Gc > hangs, so maybe that's > not the underlying problem. > > -- Paul I wondered about that as well. I think this is some uninitialized value in the GC statistics. MfG Goswin