Linked by Thom Holwerda on Wed 27th Feb 2013 22:42 UTC
Mozilla & Gecko clones "Firefox OS could actually be wildly successful, no matter how underwhelming the actual phones may be. And that's because - at least for now - you're not the customer; your carrier is." I'm extremely disappointed by Firefox OS so far. There's nothing wrong with the low-end hardware we've seen during MWC, but there is something wrong with low-end hardware that can't even properly run its operating system. To make matters worse, carriers are the boss here. Terrible first impression.
Thread beginning with comment 553995
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

You were saying? (I have 6 chrome Windows Open).

Also process isolation is a good idea, because when one tab locks up/crashes I just have to reload the tab. I am sure there are a host of other reason why it is a good idea.

Post your about:memory

Reply Parent Score: 2

lucas_maximus Member since:

I killed the process after I took the screenshot.

Reply Parent Score: 2

Alfman Member since:

I see the same memory gobbling behavior on firefox under both linux and windows.

As far as I can tell it's not related to what I'm doing, just a slow continuous leak of some sort that persists even after I close all but one tab.

about:memory doesn't look very meaningful to me, but right now with nothing but osnews open I see js-non-window at 80MB and js-main-runtime at 90MB. Everything else is much lower in comparison so a pure guess is that's it's a JS related leak. But for all I know it might be one of the plugins I've installed.

On my linux box it usually takes a week or two before firefox starts to crawl at a few gigs of ram. This happens regularly because the system is always on. On the windows side the computer is restarted every day, so although the memory usage climbs, it never becomes unusable.

I haven't tried chrome for comparison.

Reply Parent Score: 2