New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/compile: fatal error: runtime: cannot map pages in arena address space #13903
Comments
This sounds like your windows XP machine does not have enough physical On Mon, 11 Jan 2016, 11:57 visualfc notifications@github.com wrote:
|
Can you show us the output of |
Go1.5.2go version go1.5.2 windows/386 go env
gcc version
go build -x
Go1.6 beta1go version go1.6beta1 windows/386 go env
gcc version
go build -x
|
my test computer is xp Intel Pentium 4 CPU 3.07G, 2G Memory。
|
As I understand it the Windows 32 bit address space is highly fragmented, there is barely 700mb of contiguous space for the heap. It seems possible that this program is to complicated to be compiled using a 32bit compiler.
|
I can reproduce this crash. I also made change to cmd/compile so I can see all system allocations.
I must agree with Dave. You program is too complicated for cmd/compile to fit everything it needs in memory that is available on Windows 32-bit OS. It does not matter how much memory you have in your computer. The problem is that "memory address space" on Windows 32-bit is limited to 2GB, all shared by your program and all DLLs your program use. Alex |
Thanks, I now switch to go1.4.2 to compile and develop, this version version can be passed. |
You can also use any computer with Windows 64 bit OS (if you have one). Obviously also you could try and split your package functionality into many smaller packages, if possible. Alex |
Thanks, Windows 7 64 bit go1.5.2 compile passed, Linux 32/64 bit (VirtualBox) go1.5.2 compile also the same passed. Only my old windows xp computer request go1.4.2. |
I'm going to close this bug. Our compiler is a bit of a memory hog, and that causes problems on 32-bit architectures. Those architectures are memory constrained, and there's not much we can do about that. We've got lots of other open bugs about the compiler's memory use (a sampling: #15350 and #14775), and progress there will help this issue. There are available workarounds, including cross-compiling from a 64-bit machine and splitting large function bodies up. |
go version: go version go1.5.2 windows/386
go version: go1.6beta1 windows/386
operator system : windows xp
build pkg https://github.com/visualfc/goqt
Go1.4.2 compile correctly. On some machines Go1.5.2 dump
fatal error: runtime: cannot map pages in arena address space
and Go1.6 beta1 dumpfatal error: out of memory
go1.5.2 build
go1.6 beta1 build
The text was updated successfully, but these errors were encountered: