Hacker News Reader

Comment by djhworld | Hacker News Reader

Nice.

  For now, we allocate one large chunk of memory 32 MB and let  malloc and free manage it.

32mb sounds like a lot

View on HN

Build a single page javascript application and don't refresh after using it for a few hours. I've yet to find one that doesn't leak memory like a sieve.

The render process on very page you're on right now consumes 116mb, see: http://i.imgur.com/gCA1C.png

Are you on a Retina display? That screenshot is beautiful (and huge).

The size can be adjusted to whatever size you need. In principle this can be done automatically by malloc by hot-swapping the typed array with a larger one.

32 MB of heap is not any problem for modern GCs and modern RAM speeds. With a typical DDR3 memory with bandwidth of 16 GB/s that should fully GC in a few ms. And good GCs usually don't stop the mutator in the marking phase (at least so do some GCs in Java), so the total blocking time could be even lower.

Reply on news.ycombinator.com