Comment The article's premise is flawed (Score 1) 174
The article claims to measure the severity of a memory leak defect based on the amount of memory it leaked -- but most memory leaks (that are severe enough to be noticed) are small leaks that occur at regular intervals, meaning that the program's memory footprint will continually grow larger over repeated operations.
Therefore, do you want a 1MB memory leak? Run the program for a while. Do you want a 1GB memory leak? Run the program for that much longer. Keep going, and you can eventually get to any number you want, to post in your Substack article; this makes the reported numbers arbitrary and therefore meaningless.
TL;DR: Memory leaks are a problem, and they can be avoided with care and proper coding techniques, but claiming that software quality is worse now because the leaks "are larger" is silly.