[Openmcl-devel] RUN-PROGRAM and memory overcommit

[Ron Garret]

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.

According to:

http://stackoverflow.com/questions/12924048/fork-memory-allocation-behavior

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?

Thanks,
rg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clozure.com/pipermail/openmcl-devel/attachments/20140206/47203a43/attachment.bin>