[Openmcl-devel] RUN-PROGRAM and memory overcommit
ron at flownet.com
Thu Feb 6 23:36:02 UTC 2014
The other day I got an out-of-memory error on a Linux machine when calling RUN-PROGRAM from a CCL process that was consuming about 75% of the available RAM. The machine does not have a swap partition, and /proc/sys/vm/overcommit_memory was set to 0.
this error could be avoided by spawning the child process with vfork instead of fork.
Before submitting a ticket I thought I would ask: is there a reason that run-program uses fork instead of vfork?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the Openmcl-devel