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.0 required=5.0 tests=none autolearn=disabled version=3.1.3 Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by yquem.inria.fr (Postfix) with ESMTP id 55816BC69 for ; Wed, 14 Nov 2007 15:16:48 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAO6ROkdYvxGE/2dsb2JhbAA X-IronPort-AV: E=Sophos;i="4.21,417,1188770400"; d="scan'208";a="4447571" Received: from www.rastageeks.org (HELO mail.rastageeks.org) ([88.191.17.132]) by mail1-smtp-roc.national.inria.fr with ESMTP; 14 Nov 2007 15:16:48 +0100 Received: from [192.168.112.144] (sphinx.lix.polytechnique.fr [129.104.11.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.rastageeks.org (Postfix) with ESMTP id 3FCE29C433 for ; Wed, 14 Nov 2007 15:16:47 +0100 (CET) From: Romain Beauxis To: caml-list@yquem.inria.fr Subject: Re: [Caml-list] OCaml runtime using too much memory in 64-bit Linux Date: Wed, 14 Nov 2007 15:16:44 +0100 User-Agent: KMail/1.9.7 References: <4731F5D1.2070405@janestcapital.com> <8ef825670711140403m464c01detff5537abb2211946@mail.gmail.com> <473AF04C.7030107@inria.fr> In-Reply-To: <473AF04C.7030107@inria.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200711141516.44531.toots@rastageeks.org> X-Spam: no; 0.00; ocaml:01 runtime:01 distros:01 bug:01 caml-list:01 data:02 kernel:02 kernel:02 sys:03 workaround:03 patches:03 fix:05 applied:05 xavier:06 xavier:06 Hi Xavier ! Le Wednesday 14 November 2007 13:55:40 Xavier Leroy, vous avez =E9crit=A0: > Apparently, this trick is no longer working on some systems, but I > need to understand better which ones exactly. =A0(I suspect some Linux > distros that applied address randomization patches to the stock Linux > kernel.) =A0So, please provide feedback in the BTS. While printing the required data for your bug report, we found out that: /proc/sys/kernel/randomize_va_space can be set to 0 Afterward, the issue does not appear anymore. Quite a good workaround until a real fix appear.. :) Romain