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
Ah, I see. cargo run --release --features ssl get-pip.py should work on Arch Linux.
What @andrew-ld is trying now cargo run --release --all-features get-pip.py doesn't work
as it hogging all available memory.
We should be able to isolate which feature causes the issue by adding feature one by one.
I think that's just too much profiling information getting collected. Running it with other scripts (i.e try running the tests for itertools) should also lead to monstrous RAM consumption.
@andrew-ld could you check if the hanging is present? flame-it chewing up all the ram is something that I don't think will be fixed, it has its usages with scripts that don't do as much as get-pip does.
Activity
DimitrisJim commentedon Sep 27, 2021
bump, can you try running this again? I could repro when I first saw it but currently cannot.
coolreader18 commentedon Sep 27, 2021
This currently works on my machine as well, there are just some warnings which I fixed in #3158
andrew-ld commentedon Sep 30, 2021
This currently works on my machine
andrew-ld commentedon Oct 2, 2021
seems to be broken again
commit: 6b1af9a
oroppas commentedon Oct 12, 2021
Works on my Arch Linux.
andrew-ld commentedon Oct 13, 2021
from me it keeps using so much ram until it has a sigkill
oroppas commentedon Oct 13, 2021
Ah, I see.
cargo run --release --features ssl get-pip.pyshould work on Arch Linux.What @andrew-ld is trying now
cargo run --release --all-features get-pip.pydoesn't workas it hogging all available memory.
We should be able to isolate which feature causes the issue by adding feature one by one.
oroppas commentedon Oct 13, 2021
cargo run --release --features "ssl, flame-it" get-pip.pycauses memory allocation failure.DimitrisJim commentedon Oct 14, 2021
I think that's just too much profiling information getting collected. Running it with other scripts (i.e try running the tests for itertools) should also lead to monstrous RAM consumption.
DimitrisJim commentedon Oct 15, 2021
@andrew-ld could you check if the hanging is present? flame-it chewing up all the ram is something that I don't think will be fixed, it has its usages with scripts that don't do as much as
get-pipdoes.