You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible to figure out why SIGKILL was received on this build? I think that OOM is the obvious suspect since this is a huge crate with all of its documentation enabled (which we do for docs-rs). I wanted to ideally confirm though that this was OOM-killed before trying to do something else.
Otherwise, if the memory limit can't be raised, I suspect the next step is to open a bug on rustdoc itself!
The text was updated successfully, but these errors were encountered:
Is it possible to figure out why SIGKILL was received on this build?
Not without running cargo doc or a local docs.rs instance, unfortunately - I'd love to have it though: #878.
I can definitely raise the memory limit in the meantime, it will probably be a while before rustdoc's memory consumption improves (although if the cause is different here than in rust-lang/rust#79103 I'd love to hear about it 🙂)
Crate name: web-sys
Build failure link: https://docs.rs/crate/web-sys/0.3.46/builds/321002
Additional details:
Is it possible to figure out why SIGKILL was received on this build? I think that OOM is the obvious suspect since this is a huge crate with all of its documentation enabled (which we do for docs-rs). I wanted to ideally confirm though that this was OOM-killed before trying to do something else.
Otherwise, if the memory limit can't be raised, I suspect the next step is to open a bug on rustdoc itself!
The text was updated successfully, but these errors were encountered: