From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.1 required=5.0 tests=AWL autolearn=disabled version=3.1.3 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 AA447BBCA for ; Thu, 8 May 2008 15:40:15 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhUEAI+fIkjAXQImiGdsb2JhbACDHY5mAQEBDyCTbIV5 X-IronPort-AV: E=Sophos;i="4.27,455,1204498800"; d="scan'208";a="10512251" Received: from discorde.inria.fr ([192.93.2.38]) by mail2-smtp-roc.national.inria.fr with ESMTP; 08 May 2008 15:40:15 +0200 Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id m48DeEuf018072 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Thu, 8 May 2008 15:40:15 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvYEAFOfIkjRVcirc2dsb2JhbACDHY5mAQwDBAQJDwWTaYV6 X-IronPort-AV: E=Sophos;i="4.27,455,1204498800"; d="scan'208";a="12382490" Received: from wf-out-1314.google.com ([209.85.200.171]) by mail3-smtp-sop.national.inria.fr with ESMTP; 08 May 2008 15:40:13 +0200 Received: by wf-out-1314.google.com with SMTP id 25so885479wfa.0 for ; Thu, 08 May 2008 06:40:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Y3U4DSsQY3vYY5DrM5itSYycwsaI+DAwtZjIf8OKAoE=; b=pAo0NGWb/CnV9fZQHQJbdZmL3iZblSiBF6qWWcanJtQLQ/6viDmMo9TB53fcpYs8EvQH+euPAkI2WoZg6t3eH0iO+UoEKENCEkm8bprR8EHjbBbnbz+5X5RRpI8TPp6V/Ebyxmozi8W8ieiw42X3Lf/sM8e1SvJONPIwjNmxMGw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XjzRFEIQZNfsdNeWC+Kjc+7zd5UdfhxIkREbmpnNj+qiAvMJTudGOYbpB9MX+zqE8nKq0n3FGdLal42MlHez3XHhqfshuQLITDn8hiDgEoRyPMCgYeIb0XNyGZA/r4WxdpzFJELJ8uaXYPAzCAfnPYtWRcaLIzSLuYJ4tCS7ArE= Received: by 10.142.226.2 with SMTP id y2mr1408509wfg.75.1210254012834; Thu, 08 May 2008 06:40:12 -0700 (PDT) Received: by 10.143.17.15 with HTTP; Thu, 8 May 2008 06:40:12 -0700 (PDT) Message-ID: Date: Thu, 8 May 2008 09:40:12 -0400 From: "Markus Mottl" To: "Richard Jones" Subject: Re: [Caml-list] ocamlc.opt tries to allocate 34 GB of RAM ... and fails Cc: caml-list@inria.fr In-Reply-To: <20080508101413.GA18974@annexia.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080507170149.GA21077@annexia.org> <04bfd9a7e0fb697f30fc7376d28b8fa5@localhost> <20080507183424.GA24624@annexia.org> <20080507184957.GA25416@annexia.org> <20080508091449.GA16556@annexia.org> <20080508101413.GA18974@annexia.org> X-Miltered: at discorde with ID 482302BE.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; markus:01 mottl:01 markus:01 mottl:01 ocamlc:01 initialized:01 runtime:01 cvs-version:01 ocaml:01 wrote:01 heap:01 caml-list:01 implemented:02 allocated:02 seems:03 On Thu, May 8, 2008 at 6:14 AM, Richard Jones wrote: > Growing heap to 4320k bytes > Growing page table to 34359705221 entries > No room for growing page table > Fatal error: out of memory. Yeah, that's an indication that you've hit the mentioned problem (addresses of allocated memory too far apart). > Unfortunately I have no idea how to solve this, certainly it seems > there is no simple fix ... (I tried to set vm.overcommit_memory > policy, but that doesn't work because the page table is initialized > right after allocation). If my mmap "fix" (not guaranteed to work with all kernels) is in the executing runtime, then, I'm afraid, there is little you can do other than switching to a CVS-version of the upcoming OCaml-release. Xavier has implemented a completely new page table representation there, which should solve this problem once and for all. Regards, Markus -- Markus Mottl http://www.ocaml.info markus.mottl@gmail.com