Comment 1:

Issue #4379 has been merged into this issue.

Comment 2:

Labels changed: added size-l.

Comment 3 by viriketo:

I was looking at the FAQ answer about the big virtual size, compared to the resident
size (on linux i686). It mentions that it doesn't take physical memory from other
processes. I feel like the big VSIZE affects whether linux will allow the fork or not.
I'm rewriting a program from C to Go, and I noticed that at around a VSIZE=2GB and
RSS=600MB, fork/exec fails in the go version of the program. In the C version, which
doesn't have such a big VSIZE, that doesn't happen.
The machine has 4GB of RAM, no swap, and I use go 1.0.3.
May this issue be related to what I see?

Comment 4:

This issue was closed by revision 8a6ff3a.

Status changed to Fixed.