This &quot;crap&quot; is a stack overflow. The &quot;correct&quot; way of handling this crap is to terminate the process on a stack overflow (Rust does this for most stack overflows anyway). The current incorrect way causes a segfault instead, which also terminates the process -- not much of a difference for a production user; it crashes either way.<p>This can lead to bad memory reads <i>if you try really hard to write code that leads to it</i>, and that too it will happen a small fraction of the time -- all the other times it will segfault-crash (and would be caught in testing or in deployment without being exploited).