First Firefox 7 Beta Promises Dramatically Lower Memory Use

[MrXidus]

Your welcome umbra

 

[Deleted member 178]

if i want the same boolean for ff6, should i spell it like this ? : extensions.checkCompatibility.firefox

 

[MrXidus]

When I used Firefox 5.0 I used this extensions.checkCompatibility.5.0
So for 6.0 change it to extensions.checkCompatibility.6.0 and tell me if it works or not.

 

[Deleted member 178]

Nightly dont show me some RAM improvement compared to FF6 , so i switched back to the latest. the boolean works.

 

[jamescv7]

Also Firefox will also become less usage in memory once it was idle too. Good analysis MrXidus so its shows that FF patch memory consumption was working well.

 

[Jack]

To be honest, I don't think Firefox has ever had a memory issue. "Firefox uses 100-200MB of ram"... woo... 100-200MB out of how many gigs of ram?

Got 4GB RAM.....so I have to agree with you. The Ram Usage wasn't a problem for me......The RAM Usage will increase once the users will start adding plugins .... Right now I'm using 5 add ons on Chrome which take around 60MB to run and to be fair I had never even monitor how much they are using because...well.... I have 4 GB RAM . As long as everything is working fine I see no major if the browser is using 100 or 200 MB of ram to run.
The Ram Usage wasn't really a issue for Firefox,the main problem for Mozilla is that Google is building an entire world around Chrome....eg : Chrome Web Store...Did you check it out lately? They've got a ton of stuff.. And what is Mozilla doing? ... Well.....they are trying to lower the memory usage from 100 to 150.... pathetic...

 

[bogdan]

if i want the same boolean for ff6, should i spell it like this ? : extensions.checkCompatibility.firefox

According to this info on the setting extensions.checkCompatibility.6.0 might work and there is also an addon that can change that setting for you (Add-on Compatibility Reporter). However you should also consider the following:

This is useful if you are using alpha, beta or nightly (development) builds which Add-on authors do not yet support. However, enabling incompatible extensions may cause crashes or other malfunctions.

Another thing you could do is download and "hack" the extensions that do not work -> see point 2 in this article

 

[HeffeD]

However you should also consider the following:

This is useful if you are using alpha, beta or nightly (development) builds which Add-on authors do not yet support. However, enabling incompatible extensions may cause crashes or other malfunctions.

Yep. It's always a good idea to disable all add-ons but one when you're testing compatibility for this reason.

 

[jamescv7]

I tried this at the moment just to make trafficlight worked, and this is good as temporary band aid solution since its not yet updated.

 

[MrXidus]

what is Mozilla doing? ... Well.....they are trying to lower the memory usage from 100 to 150.... pathetic...

Which they have successfully done.

 

[jamescv7]

Since Firefox as only one process (exclude plugin-container) and can consume high RAM yet that's the right path on lowering the memory usage.Unlike chrome it have a multiprocesses that can equalized the consume of RAM.