4 ms·
Minor correction: firefox (at least) isn't "killed" due to memory limits. firefox segfaults because it tries to allocate memory and doesn't check for null. chro
by tedunangst 12y ago
Minor correction: firefox (at least) isn't "killed" due to memory limits. firefox segfaults because it tries to allocate memory and doesn't check for null. chrome in effect works around the memory limit by using one process per tab.