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

reflect: TestBigArgs kills machine #6033

Closed
dvyukov opened this issue Aug 4, 2013 · 3 comments
Closed

reflect: TestBigArgs kills machine #6033

dvyukov opened this issue Aug 4, 2013 · 3 comments
Milestone

Comments

@dvyukov
Copy link
Member

@dvyukov dvyukov commented Aug 4, 2013

TestBigArgs kills both my windows and darwin machines with 4GB RAM. The test eats all
available memory.
Probably my linux machine with 64GB RAM would be able to run it, but I would like to run
them of other machines as well.
@gopherbot
Copy link

@gopherbot gopherbot commented Aug 4, 2013

Comment 1 by keith.randall:

It is just testing an error message, so if it is a pain we can delete it.
Why is it using real memory and not just address space?
@dvyukov
Copy link
Member Author

@dvyukov dvyukov commented Aug 4, 2013

Comment 2:

>Why is it using real memory and not just address space?
because Go zeroes memory
@randall77
Copy link
Contributor

@randall77 randall77 commented Aug 5, 2013

Comment 3:

This issue was closed by revision f791012.

Status changed to Fixed.

@rsc rsc added this to the Go1.2 milestone Apr 14, 2015
@rsc rsc removed the go1.2maybe label Apr 14, 2015
@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
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants