Linked by Thom Holwerda on Wed 27th Feb 2013 22:42 UTC
Thread beginning with comment 553912
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: there is nothing wrong with the hardware
by renox on Mon 4th Mar 2013 14:56
in reply to "RE[3]: there is nothing wrong with the hardware"
"Yeah so ludicrous that FF devs tried to do the same thing (the Electrolysis project) but backed down because it was a too big change to their codebase..
Well, considering that the RAM problem seems to be related to it, and that with a combination of good session management and load-on-demand after a restart, the issue of pages crashing the browser is alleviated, it seems silly. "
Silly? Last I've heard they have revived the Electrolysis project for the FirefoxOS ;-)
Aaron Seigo reposted something on his blog the other day about how it was proving a limitation for web app developers, too.
I would take Aaron Seigo's post with a (big) grain of salt: 1) the link he posted, is broken now so there is no way to see if it is a good analysis or not.
2) the reason he posted this is because many criticised KDE's design where one malfunctionning plasma applet can bring down the whole desktop.
3) he 'forget' that Chrome can also be configured to have everything running in one process with a command line option..
I'm not advocating having each plasma applet running in its own process by default, but that would be handy to debug an issue with a Plasma applet, no?
Edited 2013-03-04 14:57 UTC




Member since:
2008-11-25
True, this is on GNU/Linux. After all of my addons were installed, it still felt more responsive even when I used to use windows, though (chrome needed much more addons due to lacking functionality).
Well, considering that the RAM problem seems to be related to it, and that with a combination of good session management and load-on-demand after a restart, the issue of pages crashing the browser is alleviated, it seems silly.
Aaron Seigo reposted something on his blog the other day about how it was proving a limitation for web app developers, too.
Edited 2013-02-28 10:49 UTC