Hacker News new | past | comments | ask | show | jobs | submit login

150 tabs of images isn't the same as 150 tabs of web pages, though.



That's certainly true, but Chrome ostensibly doesn't know that, and spins a new process per tab (or close to it). Creating 150 new processes, even if just to load an image in each, increases memory consumption and processor overhead.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: