If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
No announcement yet.
Firefox 28.0 Delivers VP9 Video Decoding, Opus In WebM
Firefox user here. I still have some problems with Firefox : On my 32bits (old) mini netbook, I think there's a memory leak : memory usage keep increasing, until the system is unusable. I have to call OOM_Kill manually (it even happens on safe mode, so it's not an extension problem). On my desktop, it always crashes the first time I enter the master password. I need to relaunch it and re-enter the password to use it.
So, in my opinion, Firefox is not as stable as it could be. But this come a a price to pay for a lot of really useful functionalities. And I am waiting the new multi threaded engine to see the performance gains it can bring. I also had a lot more issue with others browsers (Konqueror, Chromium, Opera...), even if I didn't try Cromium in a long time.
Firefox is getting better but it still chokes with websites after being up for two hours or more. Use a site like OKCupid for a bit with multiple tabs, leave it open for some time, and you'll see exactly what I mean.
I'm on the Aurora channel, so I'm currently running 29.0a2 and my only issue with Firefox has been how it's really a cooperatively multitasked OS in 2014. When you've got as many extensions and tabs as I do, that really causes a lot of janking.
(It does also have a tendency to leak its way up to around 6GiB resident before I restart it, but that's some extension's fault and, hopefully, e10s will make it easier for them to implement something along the lines of Chrome's task manager so I don't have to spend days living with a crippled experience while I bisect my extension collection.)
Pass `--single-process` to Chromium for an apples to apples comparison. Chromium's sandboxing comes at a high memory usage cost. It puts each site instance in an empty chroot, process namespace and network namespace. Unlike on Windows, it's able to reduce the kernel attack surface by making use of seccomp so it's not easy to bypass the sandbox.
It is not an apples to apples comparison.
* --single-process is not supported under chromium and may leads to errors and crashes, firefox works ok in native single process mode instead.
Chromium is just NOT usable in that configuration.
* I'm certainly not going to ask for a chromium option to provide the (better) framework extension firefox provides.
The apple to apple comparision is with the borwsers as they come out of the box; then you can compare reactivity, memory usage, cpu use and so on.
And, out of the box, chromium uses an excessive amount of ram, imho.
Funny thing - one of the few sites that looks like garbage on Firefox on my Android phone is Phoronix. Looks perfect on Chrome, but I can't get font sizing correct for some reason on Firefox. Half the page looks grotesquely enormous, and half the page is so tiny that it's unreadable.
That's because Michael is incapable of deploying a mobile style for Phoronix. Mobile browsers have to do some voodoo to try to find a good compromise and the result widely varies from device to device. On my Galaxy S3 it's exactly the opposite: FF works better with Phoronix than Chrome. Not only did Firefox choose font settings that make the main text readable just fine, the links in the sidebars are readable as wee but not in Chrome.
The only real fix is that website providers work on a mobile layout instead of countless useless benchmarks…