Message 217309 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	pitrou
Recipients	josh.r, jtaylor, neologix, njs, pitrou, skrah, vstinner
Date	2014-04-27.19:09:37
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1398625775.2380.6.camel@fsol>
In-reply-to	<CAH_1eM1CyDRTvhbF2OsqeP2xy2VSNhGLXmyzMRozrAH-ZYQQHw@mail.gmail.com>

Content
> Hm... > What's /proc/sys/vm/overcommit_memory ? > If it's set to 0, then the kernel will always overcommit. Ah, indeed. > If you set it to 2, normally you'd definitely get ENOMEM You're right, but with weird results: $ gcc -o /tmp/test test.c; /tmp/test malloc() returned NULL after 600MB $ gcc -DDO_MEMSET -o /tmp/test test.c; /tmp/test malloc() returned NULL after 600MB (I'm supposed to have gigabytes free?!)

> Hm...
> What's /proc/sys/vm/overcommit_memory ?
> If it's set to 0, then the kernel will always overcommit.

Ah, indeed.

> If you set it to 2, normally you'd definitely get ENOMEM

You're right, but with weird results:

$ gcc -o /tmp/test test.c; /tmp/test
malloc() returned NULL after 600MB
$ gcc -DDO_MEMSET -o /tmp/test test.c; /tmp/test
malloc() returned NULL after 600MB

(I'm supposed to have gigabytes free?!)

History
Date	User	Action	Args
2014-04-27 19:09:37	pitrou	set	recipients: + pitrou, vstinner, njs, skrah, neologix, jtaylor, josh.r
2014-04-27 19:09:37	pitrou	link	issue21233 messages
2014-04-27 19:09:37	pitrou	create