Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #13015

T

Tumblr

Personal blog · blog.kylehuey.comprogrammingsystems

Tumblr is a personal blog at blog.kylehuey.com about programming and systems. Since 2011, 6 different Hacker News readers have linked it 7 times, most often “Fixing the (Firefox) Memory Leak”. The last post was in 2020, but the archive is still widely read.

Visit the blog
7mentions?
6HN people?
2011–2013first – last linked?
Links on Hacker News per year · peak 5 in 2012

Too few sampled comments (4) to say how often HN recommends it.?

Why HN links it

HN commenters link this blog for a post on the fix for Firefox add-on memory leaks (the "Hueyfix"), cited as detailed technical background on the Firefox 13 to 15 performance work.

Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Most-linked posts?

  1. Fixing the (Firefox) Memory Leak
    4 people · 5 mentions · first linked 2012-04-27

What Hacker News says?

  1. Mozilla appears to be working on this[0], and improvements are already being seen. (Just as they are vastly improving all the other aspects detractors like to bring up, e.g. memory usage[1], including that of addons via the "Hueyfix"[2].) [0]: https://wiki.mozilla.org/Performance/Snappy [1]: https://wiki.mozilla.org/Performance/MemShrink [2]: http://blog.kylehuey.com/post/21892343371/fixing-the-memory-...

    Comment linking /post/21892343371/fixing-the-memory-leak

    on “Mozilla Gains Global Support For a Firefox Mobile OS”
  2. Submitted Fixing the (Firefox) Memory Leak as a story · 6 points

    HN discussion
  3. So far as I understand, there was a change made which cut off a leak between add-ons and the tabs/windows they were attached to, so that closed tabs weren't being held in memory just because an add-on had a reference to them. However, that change broke something in earlier versions of the Add-on SDK, which means that at least one Add-on was then leaking memory like crazy. Upgrading that add-on to the latest version…

    Comment linking /post/21892343371/fixing-the-memory-leak

    on “Firefox finally plugs the leak”
  4. Submitted Cycle Collector on Worker Threads as a story · 2 points

    HN discussion
  5. Here's some detailed information about the addon leak fix from the developer who fixed it: http://blog.kylehuey.com/post/21892343371/fixing-the-memory-...

    Comment linking /post/21892343371/fixing-the-memory-leak

    on “Firefox 15 available to download, finally fixes add-on memory leak”
  6. Submitted Pushing Compilers to the Limit (and Beyond) as a story · 2 points

    HN discussion
  7. In fact, we have recently fixed a common source of addon memory leaks: http://blog.kylehuey.com/post/21892343371/fixing-the-memory-... The version containing this fix is scheduled to be released in August, I believe.

    Comment linking /post/21892343371/fixing-the-memory-leak

    on “Getting snappy – performance optimisations in Firefox 13”

Search all of HN for blog.kylehuey.com

Linked by the same people?