i don't know about the nature of the YC.news architecture, but if it's an error that happens unexpectecly then it must be due to some scheduled automatically recurring function that fails somehow and eats up all memory...
so probably it must be on the web server or the stats logging
update: or the weighting algorithm, which is obviously a new addition