From: Goswin von Brederlow <goswin-v-b@web.de>
To: Adrien Nader <adrien@notk.org>
Cc: Amogh Margoor <Amogh.Margoor@mathworks.in>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Ocaml crash in windows due to running out of memory
Date: Mon, 25 Nov 2013 14:01:11 +0100 [thread overview]
Message-ID: <20131125130111.GC3610@frosties> (raw)
In-Reply-To: <20131120205611.GA15056@notk.org>
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
next prev parent reply other threads:[~2013-11-25 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 10:52 Amogh Margoor
2013-11-20 20:56 ` Adrien Nader
2013-11-25 13:01 ` Goswin von Brederlow [this message]
2013-11-25 13:55 ` Adrien Nader
2013-11-26 6:53 ` Florian Hars
2013-11-26 9:14 ` Goswin von Brederlow
2013-11-26 9:24 ` Adrien Nader
2013-11-26 9:02 ` Goswin von Brederlow
2013-11-26 9:22 ` Adrien Nader
-- strict thread matches above, loose matches on Subject: below --
2013-11-20 10:48 Amogh Margoor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131125130111.GC3610@frosties \
--to=goswin-v-b@web.de \
--cc=Amogh.Margoor@mathworks.in \
--cc=adrien@notk.org \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox