From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id D15887EE25 for ; Wed, 20 Nov 2013 11:48:59 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of Amogh.Margoor@mathworks.in) identity=pra; client-ip=144.212.95.218; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="Amogh.Margoor@mathworks.in"; x-sender="Amogh.Margoor@mathworks.in"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of Amogh.Margoor@mathworks.in) identity=mailfrom; client-ip=144.212.95.218; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="Amogh.Margoor@mathworks.in"; x-sender="Amogh.Margoor@mathworks.in"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@smtp2.mathworks.com) identity=helo; client-ip=144.212.95.218; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="Amogh.Margoor@mathworks.in"; x-sender="postmaster@smtp2.mathworks.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnkCAGWTjFKQ1F/anGdsb2JhbABZgkMjWVO+ZoETFg4BAQEBAQgLCQkUIQeCJwUtJjgBDB5WFwEOAQQbh3kBoAOgVo8mg1iBEgOtR4Iq X-IPAS-Result: AnkCAGWTjFKQ1F/anGdsb2JhbABZgkMjWVO+ZoETFg4BAQEBAQgLCQkUIQeCJwUtJjgBDB5WFwEOAQQbh3kBoAOgVo8mg1iBEgOtR4Iq X-IronPort-AV: E=Sophos;i="4.93,736,1378850400"; d="scan'208,217";a="44062360" Received: from smtp2.mathworks.com ([144.212.95.218]) by mail2-smtp-roc.national.inria.fr with ESMTP; 20 Nov 2013 11:48:37 +0100 Received: from mail-vif.mathworks.com (newscl01ah.mathworks.com [144.212.95.121]) by smtp2.mathworks.com (8.13.8/8.12.11) with ESMTP id rAKAmZID021453 for ; Wed, 20 Nov 2013 05:48:36 -0500 (EST) Received: from exhub-00-ah.ad.mathworks.com (exhub-00-ah.mathworks.com [172.31.22.58]) by mail-vif.mathworks.com (8.13.8/8.13.8) with ESMTP id rAKAmZO8009972 for ; Wed, 20 Nov 2013 05:48:35 -0500 (EST) Received: from exhub-01-tyo.ad.mathworks.com (172.18.90.25) by exhub-00-ah.ad.mathworks.com (172.31.22.58) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 20 Nov 2013 05:48:35 -0500 Received: from exmb-01-tyo.ad.mathworks.com ([fe80::1005:a16f:a136:6dc4]) by exhub-01-tyo.ad.mathworks.com ([::1]) with mapi id 14.03.0123.003; Wed, 20 Nov 2013 19:48:33 +0900 From: Amogh Margoor To: "caml-list@inria.fr" Thread-Topic: Ocaml crash in windows due to running out of memory Thread-Index: Ac7l3g0wIuYNHLYTSSGaB9dHwFD7yw== Date: Wed, 20 Nov 2013 10:48:31 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.90.24] Content-Type: multipart/alternative; boundary="_000_CCC7876BE807C74EABED4C8FC00ADFC5F57258exmb01tyoadmathwo_" MIME-Version: 1.0 X-Validation-by: amogh.margoor@mathworks.in Subject: [Caml-list] Ocaml crash in windows due to running out of memory --_000_CCC7876BE807C74EABED4C8FC00ADFC5F57258exmb01tyoadmathwo_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, We have memory intensive application coded in Ocaml, which crashes on Windo= ws 7 when it runs out of memory instead of throwing an exception. Is that a known issue ? Regards, Amogh --_000_CCC7876BE807C74EABED4C8FC00ADFC5F57258exmb01tyoadmathwo_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

We have memory intensive application coded in Ocaml,= which crashes on Windows 7 when it runs out of memory instead of throwing = an exception.

Is that a known issue ?

Regards,<= o:p>

Amogh

--_000_CCC7876BE807C74EABED4C8FC00ADFC5F57258exmb01tyoadmathwo_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 3D6167EE25 for ; Wed, 20 Nov 2013 11:52:47 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of Amogh.Margoor@mathworks.in) identity=pra; client-ip=144.212.95.218; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="Amogh.Margoor@mathworks.in"; x-sender="Amogh.Margoor@mathworks.in"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of Amogh.Margoor@mathworks.in) identity=mailfrom; client-ip=144.212.95.218; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="Amogh.Margoor@mathworks.in"; x-sender="Amogh.Margoor@mathworks.in"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@smtp2.mathworks.com) identity=helo; client-ip=144.212.95.218; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="Amogh.Margoor@mathworks.in"; x-sender="postmaster@smtp2.mathworks.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnkCAGWTjFKQ1F/anGdsb2JhbABZgkMjWVO+ZoETFg4BAQEBAQgLCQkUIQeCJQEBAQQtJjgBCBEEAQELVhcBBQkBBBMIh3kBoAOgVo8mg1iBEgOtR4Iq X-IPAS-Result: AnkCAGWTjFKQ1F/anGdsb2JhbABZgkMjWVO+ZoETFg4BAQEBAQgLCQkUIQeCJQEBAQQtJjgBCBEEAQELVhcBBQkBBBMIh3kBoAOgVo8mg1iBEgOtR4Iq X-IronPort-AV: E=Sophos;i="4.93,736,1378850400"; d="scan'208,217";a="44063576" Received: from smtp2.mathworks.com ([144.212.95.218]) by mail2-smtp-roc.national.inria.fr with ESMTP; 20 Nov 2013 11:52:46 +0100 Received: from mail-vif.mathworks.com (newscl01ah.mathworks.com [144.212.95.121]) by smtp2.mathworks.com (8.13.8/8.12.11) with ESMTP id rAKAqjmJ021576 for ; Wed, 20 Nov 2013 05:52:46 -0500 (EST) Received: from exhub-00-ah.ad.mathworks.com (exhub-00-ah.mathworks.com [172.31.22.58]) by mail-vif.mathworks.com (8.13.8/8.13.8) with ESMTP id rAKAqjHO013928 for ; Wed, 20 Nov 2013 05:52:45 -0500 (EST) Received: from exhub-01-tyo.ad.mathworks.com (172.18.90.25) by exhub-00-ah.ad.mathworks.com (172.31.22.58) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 20 Nov 2013 05:52:45 -0500 Received: from exmb-01-tyo.ad.mathworks.com ([fe80::1005:a16f:a136:6dc4]) by exhub-01-tyo.ad.mathworks.com ([::1]) with mapi id 14.03.0123.003; Wed, 20 Nov 2013 19:52:37 +0900 From: Amogh Margoor To: "caml-list@inria.fr" Thread-Topic: Ocaml crash in windows due to running out of memory Thread-Index: Ac7l3g0wIuYNHLYTSSGaB9dHwFD7ywAAH8ww Date: Wed, 20 Nov 2013 10:52:37 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.90.24] Content-Type: multipart/alternative; boundary="_000_CCC7876BE807C74EABED4C8FC00ADFC5F5728Aexmb01tyoadmathwo_" MIME-Version: 1.0 X-Validation-by: amogh.margoor@mathworks.in Subject: RE: [Caml-list] Ocaml crash in windows due to running out of memory --_000_CCC7876BE807C74EABED4C8FC00ADFC5F5728Aexmb01tyoadmathwo_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, The Ocaml version I am facing problem with is 3.12.1. Regards, Amogh From: Amogh Margoor Sent: Wednesday, November 20, 2013 4:19 PM To: 'caml-list@inria.fr' Subject: Ocaml crash in windows due to running out of memory Hi, We have memory intensive application coded in Ocaml, which crashes on Windo= ws 7 when it runs out of memory instead of throwing an exception. Is that a known issue ? Regards, Amogh --_000_CCC7876BE807C74EABED4C8FC00ADFC5F5728Aexmb01tyoadmathwo_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,<= /p>

The Ocaml version I am= facing problem with is 3.12.1.

Regards,

Amogh

From:= Amogh Margoor
Sent: Wednesday, November 20, 2013 4:19 PM
To: 'caml-list@inria.fr'
Subject: Ocaml crash in windows due to running out of memory

Hi,

We have memory intensive application coded in Ocaml,= which crashes on Windows 7 when it runs out of memory instead of throwing = an exception.

Is that a known issue ?

Regards,<= o:p>

Amogh

--_000_CCC7876BE807C74EABED4C8FC00ADFC5F5728Aexmb01tyoadmathwo_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 7EF907EE25 for ; Wed, 20 Nov 2013 21:56:30 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of adrien@notk.org) identity=pra; client-ip=91.121.71.147; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of adrien@notk.org designates 91.121.71.147 as permitted sender) identity=mailfrom; client-ip=91.121.71.147; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@nautica.notk.org) identity=helo; client-ip=91.121.71.147; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="postmaster@nautica.notk.org"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiYFALchjVJbeUeT/2dsb2JhbABZgweEArsEgRoWdIIlAQEFI1YQCxEEAQEBAgIFEw4CAg8FGB0BBQ4TiAWvW5EOF4EpjkIHgms1gRIDmBEBkg2DKTs X-IPAS-Result: AiYFALchjVJbeUeT/2dsb2JhbABZgweEArsEgRoWdIIlAQEFI1YQCxEEAQEBAgIFEw4CAg8FGB0BBQ4TiAWvW5EOF4EpjkIHgms1gRIDmBEBkg2DKTs X-IronPort-AV: E=Sophos;i="4.93,739,1378850400"; d="scan'208";a="44204206" Received: from nautica.notk.org ([91.121.71.147]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 20 Nov 2013 21:56:12 +0100 Received: by nautica.notk.org (Postfix, from userid 1003) id 8FBEFC009; Wed, 20 Nov 2013 21:56:11 +0100 (CET) Date: Wed, 20 Nov 2013 21:56:11 +0100 From: Adrien Nader To: Amogh Margoor Cc: "caml-list@inria.fr" Message-ID: <20131120205611.GA15056@notk.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: [Caml-list] Ocaml crash in windows due to running out of memory Hi, On Wed, Nov 20, 2013, Amogh Margoor wrote: > Hi, > The Ocaml version I am facing problem with is 3.12.1. > Regards, > Amogh > > From: Amogh Margoor > Sent: Wednesday, November 20, 2013 4:19 PM > To: 'caml-list@inria.fr' > Subject: Ocaml crash in windows due to running out of memory > > Hi, > We have memory intensive application coded in Ocaml, which crashes on Windows 7 when it runs out of memory instead of throwing an exception. > Is that a known issue ? What is the exception and how much memory is your application using at that moment? -- Adrien Nader From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 7E9507EE6B for ; Mon, 25 Nov 2013 14:01:16 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of goswin-v-b@web.de) identity=pra; client-ip=212.227.17.12; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="goswin-v-b@web.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of goswin-v-b@web.de) identity=mailfrom; client-ip=212.227.17.12; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="goswin-v-b@web.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mout.web.de) identity=helo; client-ip=212.227.17.12; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="postmaster@mout.web.de"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjwCAGNJk1LU4xEMnGdsb2JhbABZumuFToErFg4BAQEBAQYNCQkUKIIlAQEFOj8QCxEEAQEBCSUPBSgNAQUOE4duARa1Cx+IRRePBweDIIETA5gThi4Sjnw X-IPAS-Result: AjwCAGNJk1LU4xEMnGdsb2JhbABZumuFToErFg4BAQEBAQYNCQkUKIIlAQEFOj8QCxEEAQEBCSUPBSgNAQUOE4duARa1Cx+IRRePBweDIIETA5gThi4Sjnw X-IronPort-AV: E=Sophos;i="4.93,768,1378850400"; d="scan'208";a="45230484" Received: from mout.web.de ([212.227.17.12]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 25 Nov 2013 14:01:16 +0100 Received: from frosties.localnet ([37.49.32.119]) by smtp.web.de (mrweb101) with ESMTPSA (Nemesis) id 0M09ZI-1VWhHz0Ysm-00uMx8 for ; Mon, 25 Nov 2013 14:01:15 +0100 Received: from mrvn by frosties.localnet with local (Exim 4.80) (envelope-from ) id 1Vkvmq-0001f7-1b; Mon, 25 Nov 2013 14:01:12 +0100 Date: Mon, 25 Nov 2013 14:01:11 +0100 From: Goswin von Brederlow To: Adrien Nader Cc: Amogh Margoor , "caml-list@inria.fr" Message-ID: <20131125130111.GC3610@frosties> References: <20131120205611.GA15056@notk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131120205611.GA15056@notk.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Provags-ID: V03:K0:SyzbfOQvTDFffuO6iVR+V1e0ONoxoo0VDZLyrMezN8dlryyH+5H EKMDW9jzect5II4z9rGo84i7uI0p9BbtiHEURYbZCC93a0k10rP0txg1XTnd1evJvQ/lkfM u9yCkcbwZzAsjmLpDq12wBVPAhaWP94ZkIszy+95aD4/rFLKuMO2af/SZQS7NmiglgGxnhs +XDvTFya5AL4jiucRk0gw== Subject: Re: [Caml-list] Ocaml crash in windows due to running out of memory On Wed, Nov 20, 2013 at 09:56:11PM +0100, Adrien Nader wrote: > Hi, > > On Wed, Nov 20, 2013, Amogh Margoor wrote: > > Hi, > > The Ocaml version I am facing problem with is 3.12.1. > > Regards, > > Amogh > > > > From: Amogh Margoor > > Sent: Wednesday, November 20, 2013 4:19 PM > > To: 'caml-list@inria.fr' > > Subject: Ocaml crash in windows due to running out of memory > > > > Hi, > > We have memory intensive application coded in Ocaml, which crashes on Windows 7 when it runs out of memory instead of throwing an exception. > > Is that a known issue ? > > What is the exception and how much memory is your application using at > that moment? Many kernels only allocate address space on malloc() and assign pages only on use. They also support over commit of memory. Meaning applications can allocate more memory than the system has under the assumption that they won't actually use it all (or that maybe some memory will be freed before the apps actually use the memory). Due to that in many kernels malloc() basically never fails but when you use the memory and the kernel can't find any page to assign to it you get a segfault and your program crashes. You only get the exception if the malloc() fails. Now I'm not sure how windows actualy handles this but it sounds like it allows over commit. MfG Goswin From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id A28E67EE6B for ; Mon, 25 Nov 2013 14:55:28 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of adrien@notk.org) identity=pra; client-ip=91.121.71.147; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of adrien@notk.org designates 91.121.71.147 as permitted sender) identity=mailfrom; client-ip=91.121.71.147; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@nautica.notk.org) identity=helo; client-ip=91.121.71.147; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="postmaster@nautica.notk.org"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiMFAIVWk1JbeUeT/2dsb2JhbABZgweEBLkkCoErFnSCJQEBBSNWEAsRBAEBAQICBRMOAgIPBRgdAQUOE4gFrRaQZReBKY1eB4JrNYETA5gTAZISgyk7 X-IPAS-Result: AiMFAIVWk1JbeUeT/2dsb2JhbABZgweEBLkkCoErFnSCJQEBBSNWEAsRBAEBAQICBRMOAgIPBRgdAQUOE4gFrRaQZReBKY1eB4JrNYETA5gTAZISgyk7 X-IronPort-AV: E=Sophos;i="4.93,768,1378850400"; d="scan'208";a="45244643" Received: from nautica.notk.org ([91.121.71.147]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 25 Nov 2013 14:55:28 +0100 Received: by nautica.notk.org (Postfix, from userid 1003) id 1E919C009; Mon, 25 Nov 2013 14:55:27 +0100 (CET) Date: Mon, 25 Nov 2013 14:55:27 +0100 From: Adrien Nader To: Goswin von Brederlow Cc: Amogh Margoor , "caml-list@inria.fr" Message-ID: <20131125135527.GA23794@notk.org> References: <20131120205611.GA15056@notk.org> <20131125130111.GC3610@frosties> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20131125130111.GC3610@frosties> User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: [Caml-list] Ocaml crash in windows due to running out of memory Hi, On Mon, Nov 25, 2013, Goswin von Brederlow wrote: > On Wed, Nov 20, 2013 at 09:56:11PM +0100, Adrien Nader wrote: > > Hi, > > > > On Wed, Nov 20, 2013, Amogh Margoor wrote: > > > Hi, > > > The Ocaml version I am facing problem with is 3.12.1. > > > Regards, > > > Amogh > > > > > > From: Amogh Margoor > > > Sent: Wednesday, November 20, 2013 4:19 PM > > > To: 'caml-list@inria.fr' > > > Subject: Ocaml crash in windows due to running out of memory > > > > > > Hi, > > > We have memory intensive application coded in Ocaml, which crashes on Windows 7 when it runs out of memory instead of throwing an exception. > > > Is that a known issue ? > > > > What is the exception and how much memory is your application using at > > that moment? > > Many kernels only allocate address space on malloc() and assign pages > only on use. They also support over commit of memory. Meaning > applications can allocate more memory than the system has under the > assumption that they won't actually use it all (or that maybe some > memory will be freed before the apps actually use the memory). > > Due to that in many kernels malloc() basically never fails but when > you use the memory and the kernel can't find any page to assign to it > you get a segfault and your program crashes. You only get the > exception if the malloc() fails. > > Now I'm not sure how windows actualy handles this but it sounds like > it allows over commit. As far as I know, it doesn't do overcommit. Also, I doubt that would change anything: if you exhaust your address space, you cannot receive a pointer to some place since it would collide with some of your already assigned space. On 32b, allocations have to fail once you reach 2GB of memory (or 3GB depending on some settings). That said, such a scenario should probably trigger an exception but so far this is just an hypothesis which cannot be confirmed until we roughly know the memory usage. -- Adrien Nader From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id A74247EE6B for ; Tue, 26 Nov 2013 07:53:49 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of florian@hars.de) identity=pra; client-ip=212.227.17.8; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="florian@hars.de"; x-sender="florian@hars.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of florian@hars.de) identity=mailfrom; client-ip=212.227.17.8; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="florian@hars.de"; x-sender="florian@hars.de"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of postmaster@moutng.kundenserver.de designates 212.227.17.8 as permitted sender) identity=helo; client-ip=212.227.17.8; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="florian@hars.de"; x-sender="postmaster@moutng.kundenserver.de"; x-conformance=sidf_compatible; x-record-type="v=spf1" X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjQCACtElFLU4xEInGdsb2JhbABZhwu2JYJ8AQmBKBYOAQEBAQEGDQkJFCiCJgEFIxVAEQsaAgUWCwICCQMCAQIBRRMIAQGIAQGtX5EPF4EpiAuFSRaCVYFIA5gUhj+Oew X-IPAS-Result: AjQCACtElFLU4xEInGdsb2JhbABZhwu2JYJ8AQmBKBYOAQEBAQEGDQkJFCiCJgEFIxVAEQsaAgUWCwICCQMCAQIBRRMIAQGIAQGtX5EPF4EpiAuFSRaCVYFIA5gUhj+Oew X-IronPort-AV: E=Sophos;i="4.93,772,1378850400"; d="scan'208";a="45401589" Received: from moutng.kundenserver.de ([212.227.17.8]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 26 Nov 2013 07:53:49 +0100 Received: from keller.fritz.box (p4FF64675.dip0.t-ipconnect.de [79.246.70.117]) by mrelayeu.kundenserver.de (node=mrbap3) with ESMTP (Nemesis) id 0MBBob-1VtCjm2Izd-00ApRp; Tue, 26 Nov 2013 07:53:47 +0100 Received: from bessel.fritz.box ([192.168.178.41]) by keller.fritz.box with esmtp (Exim 4.80) (envelope-from ) id 1VlCWo-0002JJ-RX for caml-list@inria.fr; Tue, 26 Nov 2013 07:53:46 +0100 Message-ID: <5294457A.4020709@hars.de> Date: Tue, 26 Nov 2013 07:53:46 +0100 From: Florian Hars User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: caml-list@inria.fr References: <20131120205611.GA15056@notk.org> <20131125130111.GC3610@frosties> <20131125135527.GA23794@notk.org> In-Reply-To: <20131125135527.GA23794@notk.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 192.168.178.41 X-SA-Exim-Mail-From: florian@hars.de X-SA-Exim-Scanned: No (on keller.fritz.box); SAEximRunCond expanded to false X-Provags-ID: V02:K0:pfo5DdXED9MjCHKx0Yd/x/qf87Opq3PWkpzNjPrn5sp iFk7Ylqyyu1eYhzwhQ6Ak09Tzmvc4dy/34JbH5hl21XpAZc/uR 8R7S0lFiI/meAueNX+QUSULyNXx2zs4Eyq/DHH8Fdc340BBL1p A68DbIWPBtWRCXPNYZU2fg6PTUKmG1qoBCufwJY0wt2XIdlpuF jIL0nn0JR7FiUeaHcI/gK+XzXmn2S+/kvWyon7GTQ2n64Xrr9A cpZk7tR1I9GOFHAYwu6BTdTyZskt7Zc5nHO5nkyD5vZ7/sUtAY 1yTBiUs+GpoM/s9Ft1/bjHUkNc+ArtZdex36Aeo9gNYS1Mqm4w e7/mjl6ZoCniXUOZLnWY= Subject: Re: [Caml-list] Ocaml crash in windows due to running out of memory Am 25.11.2013 14:55, schrieb Adrien Nader: > As far as I know, it doesn't do overcommit. Also, I doubt that would > change anything: if you exhaust your address space, you cannot receive a > pointer to some place since it would collide with some of your already > assigned space. That is a non-sequitur, in modern operating systems every process gets its own space of 2^64 adresses, no matter how much physical RAM + swap is available. And the common way to get overcommitment (at least on unixoids, windows may be different) in't malloc anyway, it's fork, where both processes end up with the same address space layout, but (logically) corresponding to differen physical memory (modulo COW pages). - Florian. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 3C4B27EE6B for ; Tue, 26 Nov 2013 10:02:50 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of goswin-v-b@web.de) identity=pra; client-ip=212.227.15.4; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="goswin-v-b@web.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of goswin-v-b@web.de) identity=mailfrom; client-ip=212.227.15.4; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="goswin-v-b@web.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mout.web.de) identity=helo; client-ip=212.227.15.4; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="postmaster@mout.web.de"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArYCANJilFLU4w8EnGdsb2JhbABZulmFToEpFg4BAQEBAQYNCQkUKIIlAQEFOk8LEQQBAQEJJQ8FKA0BBSGHbgEWtisfiFaOfRaDCoETA5gThi4Sjns X-IPAS-Result: ArYCANJilFLU4w8EnGdsb2JhbABZulmFToEpFg4BAQEBAQYNCQkUKIIlAQEFOk8LEQQBAQEJJQ8FKA0BBSGHbgEWtisfiFaOfRaDCoETA5gThi4Sjns X-IronPort-AV: E=Sophos;i="4.93,773,1378850400"; d="scan'208";a="45429445" Received: from mout.web.de ([212.227.15.4]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 26 Nov 2013 10:02:49 +0100 Received: from frosties.localnet ([37.49.32.119]) by smtp.web.de (mrweb101) with ESMTPSA (Nemesis) id 0Lr2dj-1V8c033cXL-00eawO for ; Tue, 26 Nov 2013 10:02:48 +0100 Received: from mrvn by frosties.localnet with local (Exim 4.80) (envelope-from ) id 1VlEXg-0005OY-75 for caml-list@inria.fr; Tue, 26 Nov 2013 10:02:48 +0100 Date: Tue, 26 Nov 2013 10:02:48 +0100 From: Goswin von Brederlow To: caml-list@inria.fr Message-ID: <20131126090248.GA20512@frosties> References: <20131120205611.GA15056@notk.org> <20131125130111.GC3610@frosties> <20131125135527.GA23794@notk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131125135527.GA23794@notk.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Provags-ID: V03:K0:/Op4VC3oDxwBwt4lBxGenDqn/0ZEgwQs0rZnsJ0MdYe0GcQKuvk N3e/FNlBmb6nO3ZORPxHaWwItf/5dfE3zvr1TFif4tXmfjE61wSDwK61gvFuXbQ6DPUP7JT DkyzJgsyQGRuITvesArdcPxx2vJHyp9pF8o91tqPSKOnIYtALerKAoK13/l2teoH2fIFUJT 31oIsIlLiL7q+mBHvXQFA== Subject: Re: [Caml-list] Ocaml crash in windows due to running out of memory On Mon, Nov 25, 2013 at 02:55:27PM +0100, Adrien Nader wrote: > Hi, > > On Mon, Nov 25, 2013, Goswin von Brederlow wrote: > > On Wed, Nov 20, 2013 at 09:56:11PM +0100, Adrien Nader wrote: > > > Hi, > > > > > > On Wed, Nov 20, 2013, Amogh Margoor wrote: > > > > Hi, > > > > The Ocaml version I am facing problem with is 3.12.1. > > > > Regards, > > > > Amogh > > > > > > > > From: Amogh Margoor > > > > Sent: Wednesday, November 20, 2013 4:19 PM > > > > To: 'caml-list@inria.fr' > > > > Subject: Ocaml crash in windows due to running out of memory > > > > > > > > Hi, > > > > We have memory intensive application coded in Ocaml, which crashes on Windows 7 when it runs out of memory instead of throwing an exception. > > > > Is that a known issue ? > > > > > > What is the exception and how much memory is your application using at > > > that moment? > > > > Many kernels only allocate address space on malloc() and assign pages > > only on use. They also support over commit of memory. Meaning > > applications can allocate more memory than the system has under the > > assumption that they won't actually use it all (or that maybe some > > memory will be freed before the apps actually use the memory). > > > > Due to that in many kernels malloc() basically never fails but when > > you use the memory and the kernel can't find any page to assign to it > > you get a segfault and your program crashes. You only get the > > exception if the malloc() fails. > > > > Now I'm not sure how windows actualy handles this but it sounds like > > it allows over commit. > > As far as I know, it doesn't do overcommit. Also, I doubt that would > change anything: if you exhaust your address space, you cannot receive a > pointer to some place since it would collide with some of your already > assigned space. > On 32b, allocations have to fail once you reach 2GB of memory (or 3GB > depending on some settings). That said, such a scenario should probably > trigger an exception but so far this is just an hypothesis which cannot > be confirmed until we roughly know the memory usage. But what if I only have 512MB ram? I can still malloc(1G), get a pointer back and then get segfaults when I use too much of it. On 64bit systems the address space also greatly exceeds any amount of physical ram you might have. My reply was just an explanation of why ocaml would crash rather than throw an out of memory exception. MfG Goswin From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id ABF6B7EE6C for ; Tue, 26 Nov 2013 10:15:01 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of goswin-v-b@web.de) identity=pra; client-ip=212.227.17.12; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="goswin-v-b@web.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of goswin-v-b@web.de) identity=mailfrom; client-ip=212.227.17.12; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="goswin-v-b@web.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mout.web.de) identity=helo; client-ip=212.227.17.12; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="goswin-v-b@web.de"; x-sender="postmaster@mout.web.de"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArYCAFJmlFLU4xEMnGdsb2JhbABZulmCSIMGgSkWDgEBAQEBBg0JCRQogiUBAQU6PxALGAklDwUoIYgBARa2Lh+IPxeOdgeDIIETA5gThi4Sjns X-IPAS-Result: ArYCAFJmlFLU4xEMnGdsb2JhbABZulmCSIMGgSkWDgEBAQEBBg0JCRQogiUBAQU6PxALGAklDwUoIYgBARa2Lh+IPxeOdgeDIIETA5gThi4Sjns X-IronPort-AV: E=Sophos;i="4.93,773,1378850400"; d="scan'208";a="45432850" Received: from mout.web.de ([212.227.17.12]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 26 Nov 2013 10:15:01 +0100 Received: from frosties.localnet ([37.49.32.119]) by smtp.web.de (mrweb002) with ESMTPSA (Nemesis) id 0LtFAh-1VfVIV2MuJ-012mMn for ; Tue, 26 Nov 2013 10:15:00 +0100 Received: from mrvn by frosties.localnet with local (Exim 4.80) (envelope-from ) id 1VlEjS-0005QU-S5; Tue, 26 Nov 2013 10:14:58 +0100 Date: Tue, 26 Nov 2013 10:14:58 +0100 From: Goswin von Brederlow To: Florian Hars Cc: caml-list@inria.fr Message-ID: <20131126091458.GB20512@frosties> References: <20131120205611.GA15056@notk.org> <20131125130111.GC3610@frosties> <20131125135527.GA23794@notk.org> <5294457A.4020709@hars.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5294457A.4020709@hars.de> User-Agent: Mutt/1.5.21 (2010-09-15) X-Provags-ID: V03:K0:ybkRK/qDj13K6c3ALx5Tct0vAA3NU/mdrZXoEaBrmnfH0UK9uPN /xfcSyDley/WxgWPnl8a9rMYZG2cFKdvw9ZJ9AdZYHXj1uXqxkAiHpqcSdUwNHe4Iq1JaPI ePTX8Fri+Z1TMWLR9QNnYCZvV1w3RTxMuCuezXc8/fXe/yByMCTkxjbscNVmWerXwvdolI3 uPV39kb8grEF/rlVIf9uA== Subject: Re: [Caml-list] Ocaml crash in windows due to running out of memory On Tue, Nov 26, 2013 at 07:53:46AM +0100, Florian Hars wrote: > Am 25.11.2013 14:55, schrieb Adrien Nader: > >As far as I know, it doesn't do overcommit. Also, I doubt that would > >change anything: if you exhaust your address space, you cannot receive a > >pointer to some place since it would collide with some of your already > >assigned space. > > That is a non-sequitur, in modern operating systems every process > gets its own space of 2^64 adresses, no matter how much physical RAM Or 2^48 on amd64 due to hardware limits. 2^47 under xen. Still plenty more than physical ram. > + swap is available. And the common way to get overcommitment (at > least on unixoids, windows may be different) in't malloc anyway, > it's fork, where both processes end up with the same address space > layout, but (logically) corresponding to differen physical memory > (modulo COW pages). > > - Florian. Note: malloc() of larger regions usualy uses mmap(), which inside the kernel sets up a COW region. So basically the same as fork(). Both are causes for overcommit. MfG Goswin From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 8733C7EE6C for ; Tue, 26 Nov 2013 10:22:51 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of adrien@notk.org) identity=pra; client-ip=91.121.71.147; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of adrien@notk.org designates 91.121.71.147 as permitted sender) identity=mailfrom; client-ip=91.121.71.147; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@nautica.notk.org) identity=helo; client-ip=91.121.71.147; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="postmaster@nautica.notk.org"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgMFAFRnlFJbeUeT/2dsb2JhbABZgweEBLkSCoEpFnSCJQEBBSNWEAsRBAEBAQICBRMOAgIPBRgdAQUOE4gFrgKREheBKY1NB4JrNYETA5gTAZIRgyk7 X-IPAS-Result: AgMFAFRnlFJbeUeT/2dsb2JhbABZgweEBLkSCoEpFnSCJQEBBSNWEAsRBAEBAQICBRMOAgIPBRgdAQUOE4gFrgKREheBKY1NB4JrNYETA5gTAZIRgyk7 X-IronPort-AV: E=Sophos;i="4.93,773,1378850400"; d="scan'208";a="45434947" Received: from nautica.notk.org ([91.121.71.147]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 26 Nov 2013 10:22:51 +0100 Received: by nautica.notk.org (Postfix, from userid 1003) id 0E1D2C009; Tue, 26 Nov 2013 10:22:50 +0100 (CET) Date: Tue, 26 Nov 2013 10:22:50 +0100 From: Adrien Nader To: Goswin von Brederlow Cc: caml-list@inria.fr Message-ID: <20131126092250.GA904@notk.org> References: <20131120205611.GA15056@notk.org> <20131125130111.GC3610@frosties> <20131125135527.GA23794@notk.org> <20131126090248.GA20512@frosties> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20131126090248.GA20512@frosties> User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: [Caml-list] Ocaml crash in windows due to running out of memory On Tue, Nov 26, 2013, Goswin von Brederlow wrote: > On Mon, Nov 25, 2013 at 02:55:27PM +0100, Adrien Nader wrote: > > Hi, > > > > On Mon, Nov 25, 2013, Goswin von Brederlow wrote: > > > On Wed, Nov 20, 2013 at 09:56:11PM +0100, Adrien Nader wrote: > > > > Hi, > > > > > > > > On Wed, Nov 20, 2013, Amogh Margoor wrote: > > > > > Hi, > > > > > The Ocaml version I am facing problem with is 3.12.1. > > > > > Regards, > > > > > Amogh > > > > > > > > > > From: Amogh Margoor > > > > > Sent: Wednesday, November 20, 2013 4:19 PM > > > > > To: 'caml-list@inria.fr' > > > > > Subject: Ocaml crash in windows due to running out of memory > > > > > > > > > > Hi, > > > > > We have memory intensive application coded in Ocaml, which crashes on Windows 7 when it runs out of memory instead of throwing an exception. > > > > > Is that a known issue ? > > > > > > > > What is the exception and how much memory is your application using at > > > > that moment? > > > > > > Many kernels only allocate address space on malloc() and assign pages > > > only on use. They also support over commit of memory. Meaning > > > applications can allocate more memory than the system has under the > > > assumption that they won't actually use it all (or that maybe some > > > memory will be freed before the apps actually use the memory). > > > > > > Due to that in many kernels malloc() basically never fails but when > > > you use the memory and the kernel can't find any page to assign to it > > > you get a segfault and your program crashes. You only get the > > > exception if the malloc() fails. > > > > > > Now I'm not sure how windows actualy handles this but it sounds like > > > it allows over commit. > > > > As far as I know, it doesn't do overcommit. Also, I doubt that would > > change anything: if you exhaust your address space, you cannot receive a > > pointer to some place since it would collide with some of your already > > assigned space. > > On 32b, allocations have to fail once you reach 2GB of memory (or 3GB > > depending on some settings). That said, such a scenario should probably > > trigger an exception but so far this is just an hypothesis which cannot > > be confirmed until we roughly know the memory usage. > > But what if I only have 512MB ram? I can still malloc(1G), get a > pointer back and then get segfaults when I use too much of it. On > 64bit systems the address space also greatly exceeds any amount of > physical ram you might have. > > My reply was just an explanation of why ocaml would crash rather than > throw an out of memory exception. OK. However as far as I know and as far as I can read right now, Windows doesn't do overcommit. Actually I'm seeing that VMWare implements its own kind of memory overcommit to save memory on the hosts. If you don't have enough memory, Windows (in its default configuration) will expand its swap files. I believe that on Windows 7 the outdated rule of swap = 2.5*RAM is still used so even with only 512MB of memory (which is something you'll have trouble finding on Windows 7 machines) you already get almost 2GB; and since Windows will happily expand swap to let your machine crawl more by using more swap, I'm sure you can almost always have 2GB usable for one process. Another efficient way to fill up 2GB of address space is mmap() or WindowsEquivalentEx() which are accessible through Bigarray. In any case, it's all speculation until we get an idea of how much memory is used by the application which crashes. -- Adrien Nader From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 68E607EE6C for ; Tue, 26 Nov 2013 10:24:28 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of adrien@notk.org) identity=pra; client-ip=91.121.71.147; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of adrien@notk.org designates 91.121.71.147 as permitted sender) identity=mailfrom; client-ip=91.121.71.147; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@nautica.notk.org) identity=helo; client-ip=91.121.71.147; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="postmaster@nautica.notk.org"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgMFAJRnlFJbeUeT/2dsb2JhbABZgweEBLYWgnwKgSkWdIIlAQEFI1YQCxgCAgUTDgICDwUYMYgYrgWREheBKY1NB4JrNYETA5gTAZIRgyk7 X-IPAS-Result: AgMFAJRnlFJbeUeT/2dsb2JhbABZgweEBLYWgnwKgSkWdIIlAQEFI1YQCxgCAgUTDgICDwUYMYgYrgWREheBKY1NB4JrNYETA5gTAZIRgyk7 X-IronPort-AV: E=Sophos;i="4.93,773,1378850400"; d="scan'208";a="37961791" Received: from nautica.notk.org ([91.121.71.147]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 26 Nov 2013 10:24:27 +0100 Received: by nautica.notk.org (Postfix, from userid 1003) id AB910C009; Tue, 26 Nov 2013 10:24:26 +0100 (CET) Date: Tue, 26 Nov 2013 10:24:26 +0100 From: Adrien Nader To: Florian Hars Cc: caml-list@inria.fr Message-ID: <20131126092426.GB904@notk.org> References: <20131120205611.GA15056@notk.org> <20131125130111.GC3610@frosties> <20131125135527.GA23794@notk.org> <5294457A.4020709@hars.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <5294457A.4020709@hars.de> User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: [Caml-list] Ocaml crash in windows due to running out of memory On Tue, Nov 26, 2013, Florian Hars wrote: > Am 25.11.2013 14:55, schrieb Adrien Nader: > >As far as I know, it doesn't do overcommit. Also, I doubt that would > >change anything: if you exhaust your address space, you cannot receive a > >pointer to some place since it would collide with some of your already > >assigned space. > > That is a non-sequitur, in modern operating systems every process > gets its own space of 2^64 adresses, no matter how much physical RAM > + swap is available. And the common way to get overcommitment (at > least on unixoids, windows may be different) in't malloc anyway, > it's fork, where both processes end up with the same address space > layout, but (logically) corresponding to differen physical memory > (modulo COW pages). I probably didn't make that clear: I'm only talking about 32 bit processes. These are still very common on Windows. Btw, you don't have fork() on Windows. Memory sharing is not done in the same way at all. -- Adrien Nader