Mozilla making progress with Firefox’s long journey to multiprocess

lxskllr

No Lifer
Nov 30, 2004
60,045
10,534
126
Meh... I had more problems with multi process Chrome than I ever had with Firefox. That was a long time ago, so it should be better now, but no problem is still no problem. "working correctly" is a hard standard to beat.
 

Chiefcrowe

Diamond Member
Sep 15, 2008
5,056
199
116
On all the computers I work on and use, I don't see flash crashing but maybe when they finalize the multiple processes it will be even more crash resistant.
 

ninaholic37

Golden Member
Apr 13, 2012
1,883
31
91
Placeholder said:
Many assume that the animal in the Firefox logo is a fox, yet Firefox is actually the nickname for the rare red panda species.

Slightly larger than a domestic cat, the red panda is native to the Himalayas and western China.

Eating mostly bamboo, it is currently classified as "vulnerable" by IUCN because of it's dwindling population.

http://en.wikipedia.org/wiki/Red_panda
Hmm... this is news to me. :)
 

zebrax2

Senior member
Nov 18, 2007
977
70
91
He was actually corrected by a later post

Actually, the animal in the logo has been specifically identified by Mozilla as a red fox (Vulpes vulpes), not a red panda (Ailurus fulgens). So in order to press home the joke, Mozilla supports red panda conservation efforts (https://blog.mozilla.org/blog/2010/12/03/meet-the-newest-and-cutest-mozillians/) and Ars gleefully adds to the confusion by using pictures of red pandas in their Firefox articles, resulting in the inevitable red panda/red fox/firefox nomenclature arguments.

The biggest plus from multiprocessing seems to be the security benefits
 
Last edited:

Revolution 11

Senior member
Jun 2, 2011
952
79
91
Oh great, now Firefox will gobble as much RAM as Chrome does. You still can't beat a Firefox browser in opening and handling vast amounts of loaded tabs.
 

lxskllr

No Lifer
Nov 30, 2004
60,045
10,534
126
Oh great, now Firefox will gobble as much RAM as Chrome does. You still can't beat a Firefox browser in opening and handling vast amounts of loaded tabs.

That's what I'm afraid of. They'll make a theoretical technical improvement that degrades real world usage. I'll wait and see. Fear is no reason to hold back software, but improvements made should definitely be improvements. They shouldn't be afraid of holding back deployment, or shelving it if it doesn't make real world browsing better.