Rust: Investigating an Out of Memory Error
5 comments
·January 15, 2025xgb84j
prerok
Well, based on the article, if there was a memory leak then they should see the steady increase in memory consumption, which was not the case.
The only explanation I can see (if their conclusion is accurate) is that the end result of the symbolization is more than 400MB additional memory consumption (which is a lot in my opinion), however the process of the symbolization requires more than 2GB additional memory (which is incredibly a lot).
oguz-ismail
[flagged]
BimJeam
I once had a faulty python based ai image generator running on my machine that used all 64 gigs of ram and oomed with a memory dump written to fs. This is no fun when that happens. But mostly these kind of bugs are misconfigurations or bad code, never ending while loops, whatever.
malkia
Can't they print something that llvm-symbolizer would pick up offline?
In the article they talk about how printing an error from the anyhow crate in debug format creates a full backtrace, which leads to an OOM error. This happens even with 4 GB of memory.
Why does creating a backtrace need such a large amount of memory? Is there a memory leak involved as well?