From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id q2OE0OWF021798 for ; Sat, 24 Mar 2012 15:00:25 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuEBAAXTbU/ZSMD3imdsb2JhbABEuCAiAQEBCgkNBxIFJIIJAQEEATpECwshJQ8BBA0bNIgFCbg8iXFxgyKDJASbPYVUh2SBUw X-IronPort-AV: E=Sophos;i="4.73,641,1325458800"; d="scan'208";a="151030124" Received: from fmmailgate06.web.de ([217.72.192.247]) by mail1-smtp-roc.national.inria.fr with ESMTP; 24 Mar 2012 15:00:25 +0100 Received: from moweb001.kundenserver.de (moweb001.kundenserver.de [172.19.20.114]) by fmmailgate06.web.de (Postfix) with ESMTP id 75196103E9E3 for ; Sat, 24 Mar 2012 15:00:24 +0100 (CET) Received: from frosties.localnet ([95.208.118.96]) by smtp.web.de (mrweb002) with ESMTPA (Nemesis) id 0LgHau-1Sf1cy1UgO-00oWJ8; Sat, 24 Mar 2012 15:00:24 +0100 Received: from mrvn by frosties.localnet with local (Exim 4.77) (envelope-from ) id 1SBRW3-0004Zp-Qp for caml-list@inria.fr; Sat, 24 Mar 2012 15:00:23 +0100 From: Goswin von Brederlow To: caml-list@inria.fr References: <874ntgadal.fsf@frosties.localnet> Date: Sat, 24 Mar 2012 15:00:23 +0100 In-Reply-To: (Hans Ole Rafaelsen's message of "Fri, 23 Mar 2012 10:32:56 +0100") Message-ID: <87obrm3xqg.fsf@frosties.localnet> 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 X-Provags-ID: V02:K0:VY6qD70SqKrRUKVNqC9p6472FRpgudIUqPTe1zQL58x IRpILijZ/FnppsAR+KSwHyyIgJvOsjm5NcoLGJi0Cq8gHotZer nRAiVKMhIEhxX5DJtuK1mziaYXMpardhKOB0tG0ZeNFWdr7eqz 8Yp8l/2tiiOthYL3g5bZis6J5jvx0vYyVWeZ3wvh5Wv95IK1fn MAAjtMeuXXB+YkU5zIpvQ== Subject: Re: [Caml-list] Strategies for finding memory leaks Hans Ole Rafaelsen writes: > Hi, > > I have tried to trigger Gc.compact but that only have limited effect for a > short time. > > Hans Ole My thinking was rather that something triggers the GC manually and over time starts to do that far too often so more and more time is spend in the GC. If it isn't triggered manually then custom types can also give the GC a wrong idea about how much memory is used/wasted. But that is also just an idea of where to look. MfG Goswin