Could you please provide more information about your software (browser, OS, clean profile?) and hardware (esp. RAM and virtual memory) configuration?
I cannot reproduce, but I've got a fairly beefed up development notebook (16GB RAM, no swap).
Anyway, out of memory errors in JavaScript, except for some stack exhaustion situations (but there's no recursive code involved in this case, as far as i can tell) or some obvious infinite loop forcing repeated allocations, are very unusual and hard to fix, since memory is managed by the runtime (with the notable exception of the recently introduced array buffers, which are not involved either). Last time I've seen one out of these scenarios, it was a browser bug.

I've reproduced it. i'm using trisquel 8 with abrowser 61.0.1, a derivative of firefox. My system has 8 gigs of memory, mostly free. It doesn't happen on the first load of https://trisquel.info. It happens if I go there, then click on a blog post link, like https://trisquel.info/en/trisquel-90-development-plans, then click back, then click the blog post below it, then click back again. On that page load, I get the error in console. If I hit f5, it happens again. If I hit ctrl-f5, it does not happen and I have to go to the other blog post pages again.

OK, thanks for the steps to reproduce. I managed to. Investigating...

This should be fixed by pull request #13

It was, thanks!