3 ms·
In my experience, Safari (and old Edge) were more willing to let pages crash or limit CPU cycles for the sake of system performance, while Chrome is content to
by ascagnel_ 5y ago
In my experience, Safari (and old Edge) were more willing to let pages crash or limit CPU cycles for the sake of system performance, while Chrome is content to let pages allocate as much RAM and use up as many CPU cycles as they want, letting poorly behaved websites work while sacrificing the rest of the system and battery life.