3 ms·
In the Haskell world there's a bit of a cheap differentiation for this kind of leak. Memory leak: classical C style, fully lost in memgrind (runtime bug) Space
by ongy 3y ago
In the Haskell world there's a bit of a cheap differentiation for this kind of leak.
Memory leak: classical C style, fully lost in memgrind (runtime bug)
Space leak: Some memory structure requires significantly more memory than it should. E.g. keeping a (lazy) ref to a large blob, around that keeps it in memory.
The effect is largely the same, but the latter is almost harder to spot, since the tooling cannot be as general as memgrind.
- crotchfire 3y agoAlso the latter is the bane of lazy languages, which make space leaks both commonplace and extremely difficult to notice.
- saagarjha 3y agoGenerally having a reference for something for longer than you should is a different kind of problem from “the vector never resizes down”.