Skip to content

Comment on Debugging hidden memory leaks in Rubyparent

Comments

I did in fact search for "RSS memory" and found what I was looking for, but I personally thought it was unclear from context what it was as RSS itself has a very strong association with another acronym (full disclosure: at the beginning of the article I though "consuming 128 MB of RSS" meant that this was an RSS parser that leaked memory) and I was more familiar with the term as a process's "working set size" rather than "resident set size".

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.