Skip to content
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

runtime: allow arenas larger than 16 GB #2385

Closed
gopherbot opened this issue Oct 20, 2011 · 7 comments
Closed

runtime: allow arenas larger than 16 GB #2385

gopherbot opened this issue Oct 20, 2011 · 7 comments

Comments

@gopherbot
Copy link
Contributor

by seanerussell:

What steps will reproduce the problem?
1. Compile the attached file (steps to compile listed below)
2. Execute on Windows
3. Watch the memory use with Resource Monitor

The application memory use increases at a rate of about 1KB every 5s until it exceeds
the stack (heap?) space and crashes.

I'm using Go 6d7136d74b65 weekly/weekly.2011-10-18 and am compiling on Linux,
cross-compiling for Windows using gb (go-gb.googlecode.com) via "GOOS=windows
gb"; 6g/l are the compilers being used.

The Linux machine is 2.6.32-32-generic #62-Ubuntu SMP, and the code is executing on
Windows Server 2008 R2 Standard, 6-core AMD Opteron 2425 HE 2.1GHz x 2, 32GB RAM, 64-bit.

I don't see similar behavior on Linux; the process memory use does grow very slowly for
a while, but appears to eventually plateau after a few minutes.

If this isn't a memory leak, but is explained by expected behavior, could I get a
pointer to a document describing the cause?

Attachments:

  1. memconsumer.go (1308 bytes)
@alexbrainman
Copy link
Member

Comment 1:

Sorry, can't help you here. I don't have PC with that much memory even to check your
program properly. Your program crashes while allocating 17GB array. It fails with
message:
throw: runtime: cannot map pages in arena address space
Looking close I can see Windows VirtualAlloc function fails trying to commit 17GB of
earlier reserved memory (MEM_COMMIT). The error message I get is ERROR_PATH_NOT_FOUND -
not sure what that means.
Your program won't even compile for GOARCH=386:
memconsumer.go:25: type [17000]Item larger than address space
Perhaps, other will help.
Alex

Owner changed to @alexbrainman.

Status changed to HelpWanted.

@rsc
Copy link
Contributor

rsc commented Oct 21, 2011

Comment 2:

If you are really allocating 17 GB, that won't work on any platform.
Go's memory allocator has a (for now) limit of 16 GB allocated.

@rsc
Copy link
Contributor

rsc commented Dec 9, 2011

Comment 3:

Labels changed: added priority-later.

@rsc
Copy link
Contributor

rsc commented Dec 12, 2011

Comment 4:

Labels changed: added priority-go1.

@robpike
Copy link
Contributor

robpike commented Jan 13, 2012

Comment 5:

Owner changed to builder@golang.org.

@rsc
Copy link
Contributor

rsc commented Jan 24, 2012

Comment 6:

Labels changed: added priority-later, removed priority-go1.

@rsc
Copy link
Contributor

rsc commented Mar 26, 2012

Comment 7:

Status changed to Duplicate.

Merged into issue #2142.

@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants