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

Jump to bottom

Mips crash on vm/cc/EvalExpressionExhaustCIDs #20056

Closed
whesse opened this issue Jul 15, 2014 · 10 comments
Closed

Mips crash on vm/cc/EvalExpressionExhaustCIDs #20056

whesse opened this issue Jul 15, 2014 · 10 comments
Assignees
@kodandersson
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.

Comments

@whesse
Copy link
Member

whesse commented Jul 15, 2014

Probably between revisions 38126 and 38141, mips hardware started crashing on the test vm/cc/EvalExpressionExhaustCIDs. This is a consistent crash, that happens almost every time on release_checked mode. In a case where it passed, in release_unchecked mode, it was the longest running test, at 95 seconds.

FAILED: none-vm-checked release_mips vm/cc/EvalExpressionExhaustCIDs
Expected: Pass
Actual: Crash
CommandOutput[run_vm_unittest]:

I notice when running the test that it takes huge amounts of memory:
0 1385m 780m 1904 D 7.1 80.1 0:58.30 run_vm_tests

We added swap, so it doesn't immediately crash when using all of the 1 GB ram on the machine, but the memory usage could be the problem causing the crash. I don't have a crash dump yet.
@iposva-google
Copy link
Contributor

Set owner to @rmacnak-google.
Added Accepted label.

@whesse
Copy link
Member Author

whesse commented Jul 15, 2014

When the swap is turned off, the process crashes with signal 9 (exit 137), due to out-of-memory. I still don't have a dump in other cases.

@iposva-google
Copy link
Contributor

Bill, I think we have plenty of indication where this is coming from. The first step would be to skip this test on MIPS until we have beefier HW.

@whesse
Copy link
Member Author

whesse commented Jul 15, 2014

OK. I'll make a CL.

@rmacnak-google
Copy link
Contributor

r38315

Added Fixed label.

@whesse
Copy link
Member Author

whesse commented Sep 1, 2014

This test still takes 700 MB resident in release mode, and more in debug mode, where it is killed. So it started failing again. Either something happened to undo the fix made in r38315, ore something else happened to increase memory usage again. The memory usage seems to be at least 10 kB per expression evaluation, since the loop runs 65536 times.

Skipping the test in the status file.

Added Triaged label.

@iposva-google
Copy link
Contributor

Added Accepted label.

@rmacnak-google
Copy link
Contributor

Stable size grows after r39688.

cc @kodandersson.

@kodandersson
Copy link
Contributor

Set owner to @kodandersson.

@kodandersson
Copy link
Contributor

The recent increase in resident size was caused by missing usage tracking; fixed in r39785.

Added Fixed label.

@whesse whesse added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. labels Sep 2, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kodandersson kodandersson

Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@whesse @iposva-google @rmacnak-google @kodandersson