Possible confusion between "memory leak" and "stack overflow"

[zhaop]

In "6.2 What is Debugging?", there's the following:

[...] sometimes they get caught in terrible loops and fill up the memory and choke all the resources of the computer until it has to be restarted. That’s called a stack overflow. Sometimes a request goes too hard, for example, calling itself so many times that the stack, which is a finite resource, fills up and can’t take it anymore.
https://github.com/BloombergMedia/whatiscode/blob/master/index.html#L2204, (bold emphasis mine)

Wouldn't "[filling] up the memory and [chocking] all the resources of the computer" rather be a memory leak, and "calling itself so many times that the stack [...] fills up and can't take it anymore" a stack overflow instead?

[emilng]

this is fixed in my pull request - #115