4 ms·

I think it's pretty clear that Chrome won the battle and Firefox is going nowhere but down. Personally, I can't see it happen fast enough. The security of Fire

I think it's pretty clear that Chrome won the battle and Firefox is going nowhere but down. Personally, I can't see it happen fast enough. The security of Firefox is (and always has been) atrocious to say the least, and will get you owned. This is not just my personal assessment, but a widely held opinion amongst security experts. On top of that the codebase is completely rotten (personal opinion). I can run Chrome for months, without crashes but Firefox can't stay running for more than a couple of days, not to mention leaking memory like no tomorrow.

turc1656 9y ago
The memory leaking is a legit issue. I've noticed the same thing. I can close a bunch of tabs and the memory usage will go down but not by anywhere near appropriate. After a long while (days), having just a small handful of tabs open will show a significant memory usage. At that point, the only solution is to close the browser and re-open it. The problem seems to be mitigated in part by using private browsing mode. It doesn't really solve the problem but if I know I'm going to be browsing script heavy sites or opening a ton of tabs for research or something, I'll open up private browsing. When I'm done, I close that private browsing window and the memory is completely released because Firefox walls off everything in private mode.
sp332 9y ago
Firefox's security suffered for a couple of years while attention was taken up by the move to multiprocess. A lot of the security effort in the near future will be adding more sandbox features to the multiprocess code. The situation has already improved over the last year, for example being added back into Pwn2Own 2017. Also memory leaks have been aggressively fixed and new ones are treated as bugs. It even limits the amount of RAM that add-ons are allowed to hog. If you can reproduce it, please submit a bug report.

turc1656 9y ago

The memory leaking is a legit issue. I've noticed the same thing. I can close a bunch of tabs and the memory usage will go down but not by anywhere near appropriate. After a long while (days), having just a small handful of tabs open will show a significant memory usage. At that point, the only solution is to close the browser and re-open it. The problem seems to be mitigated in part by using private browsing mode. It doesn't really solve the problem but if I know I'm going to be browsing script heavy sites or opening a ton of tabs for research or something, I'll open up private browsing. When I'm done, I close that private browsing window and the memory is completely released because Firefox walls off everything in private mode.

sp332 9y ago

Firefox's security suffered for a couple of years while attention was taken up by the move to multiprocess. A lot of the security effort in the near future will be adding more sandbox features to the multiprocess code. The situation has already improved over the last year, for example being added back into Pwn2Own 2017. Also memory leaks have been aggressively fixed and new ones are treated as bugs. It even limits the amount of RAM that add-ons are allowed to hog. If you can reproduce it, please submit a bug report.