2 ms·
I've been looking for evidence that the bug's been fixed, but even upon bringing up the issue with Mozilla engineers, all they have to say is "turn overcommit b
by LoganDark 4y ago
I've been looking for evidence that the bug's been fixed, but even upon bringing up the issue with Mozilla engineers, all they have to say is "turn overcommit back on, we don't support your configuration".
Excuse me, Mozilla? Firefox should not be collecting 20-30 gigabytes of committed memory in the first place. They must be high or something.