From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by yquem.inria.fr (Postfix) with ESMTP id B1002BC57 for ; Sun, 15 Aug 2010 07:57:09 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsCABIeZ0xKfVK0kGdsb2JhbACTOo0JCBUBAQEBCQkMBxEDH54BmTyFOwSJYg X-IronPort-AV: E=Sophos;i="4.55,370,1278280800"; d="scan'208";a="57108051" Received: from mail-wy0-f180.google.com ([74.125.82.180]) by mail2-smtp-roc.national.inria.fr with ESMTP; 15 Aug 2010 07:57:09 +0200 Received: by wya21 with SMTP id 21so5275365wya.39 for ; Sat, 14 Aug 2010 22:57:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.12.8 with SMTP id 8mr1221768wey.107.1281851828794; Sat, 14 Aug 2010 22:57:08 -0700 (PDT) Received: by 10.216.154.79 with HTTP; Sat, 14 Aug 2010 22:57:08 -0700 (PDT) X-Originating-IP: [110.33.116.174] Date: Sun, 15 Aug 2010 15:57:08 +1000 Message-ID: Subject: More re GC hanging From: Paul Steckler To: caml-list@yquem.inria.fr Content-Type: text/plain; charset=ISO-8859-1 X-Spam: no; 0.00; steckler:01 steck:01 verbose:01 computed:01 12.:98 garbage:01 integer:01 heap:01 heap:01 minor:01 minor:01 hangs:01 allocated:02 bytes:03 bytes:03 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