4 ms·
This is because Chrome stays in memory even when closed where Firefox doesn't.
by thrombos 10y ago
This is because Chrome stays in memory even when closed where Firefox doesn't.
- febed 10y agoI thought this was the case too, so I tried letting Firefox stay in memory using the Minimizetotray extension but it was still lagging. I had e10s enabled with just ublock origin enabled. I quit trying to optimize it further and switched back to Chrome.