-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Memory usage regression in #49045 #50073
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
It doesn't look like it #49045 creates crazy memory regressions at least: http://perf.rust-lang.org/compare.html?start=56714acc5eb0687ed9a7566fdebe5528657fc5b3&end=7222241e7c2d7caf9ad6ee6e34748e4addfb8dd3&stat=max-rss Could you run this with
|
After upgrading to The version we used before upgrading was nightly-2018-01-12, which worked fine. |
@BusyJay Interesting. What error message do you encounter? Is it same as what described in this issue? Also, can you try 2018-04-04 which should be before the problematic change? |
What I saw was:
OOM exists since |
@BusyJay I think that's a different issue. Please create an new issue optionally with bisecting the bad build. |
It seems like we need more data before we can figure out how to proceed -- |
I guess that this is a problem bootstrapping, so we ought to be able to measure the memory usage requirement locally. |
@Zoxc are you able to do a little probing? |
triage: P-high Classifying as P-high to try and get more information on what is happening. Assigning Zoxc for the time being. |
On the CircleCI Docker remote machine which has 2 cores and 8G memory, I'm no longer able to compile rustc. This error consistently occurs in stage1. This was bisected to #49045.
It's likely that overcommit is disabled and
vfork()
resulted in rejection, although I wasn't able to obtain any further traces about this.The possible cause may be:
cc @Zoxc
The text was updated successfully, but these errors were encountered: