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

Test suite OOMs unsupported architecture machines #1563

Closed
wthrowe opened this Issue Oct 29, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@wthrowe

wthrowe commented Oct 29, 2015

rr forks and the child stops itself waiting for the parent to ptrace and restart it. After the fork, the parent creates a Task, which has the side effect of checking that the CPU architecture is supported and aborting if it isn't. In that case, the child is left stopped and reparented to init. As the child uses roughly 50 MB of RAM and there are 1340 tests, the test suite quickly tries to consume roughly 67 GB of memory. That will have very unfortunate effects on many machines.

@rocallahan

This comment has been minimized.

Show comment
Hide comment
@rocallahan

rocallahan Oct 29, 2015

Member

Oops! In fact, I guess any abnormal exit between fork() and PTRACE_SEIZE will cause a process to be leaked.

Member

rocallahan commented Oct 29, 2015

Oops! In fact, I guess any abnormal exit between fork() and PTRACE_SEIZE will cause a process to be leaked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment