-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Memory usage regression since 5/1 #50389
Comments
Although I'm not absolutely confident as I haven't performed a bisect, and perf data is not updated yet as well. |
What exactly are you doing to reproduce this? Is that a reference to an earlier issue? (I vaguely remember an issue about this maybe...?) |
@nikomatsakis It's a reference to #50073. Basically, I mean that the OOM error happened again on that environment:
|
@ishitatsuyuki thanks! perf is still not updated, it seems. #50197 could certainly be the cause, that could increase the size of the interning tables. |
triage: P-high -- we're investigating. First thing is to get the perf server up and going again, probably. ( cc @Mark-Simulacrum ) |
Scanning the current max-rss statistics of perf.rust-lang.org doesn't show much that's suspicious (no recent spikes up) |
What I currently know is that compiling stage1 is taking much more memory at peak, compared to stage0. It's like 5G vs 3G. |
As of today it seems to compile successfully; so this is no longer critical. I will reopen if this happens again. |
It's back, caused by presumably #50197.
cc @nikomatsakis
The text was updated successfully, but these errors were encountered: