Recommended Posts

Few Summaries:

Firefox Nightly is now on 11 wagon.

Electrolysis Project is now slow down to get short term wins.

MemShrink also now on lower priority (if I correctly understand).

Responsiveness in now main focus.

Few Bugs:

https://bugzilla.mozilla.org/show_bug.cgi?id=666446

Landed once again. Now lets see it will be how soon backout.. (joking!!)

Incremental GC dependent bug getting little attention from developers. Also other patches paving way for it. Sweet!!

Little progress for Removal of Trace Monkey from m-c is also done. (17k lines code removal - big code is gone say bye bye)

Object Shrink projects is also underway - which will reduce significant memory usage and lesser fragmentation.

Few Summaries:

Firefox Nightly is now on 11 wagon.

Electrolysis Project is now slow down to get short term wins.

MemShrink also now on lower priority (if I correctly understand).

Responsiveness in now main focus.

Few Bugs:

https://bugzilla.moz...g.cgi?id=666446

Landed once again. Now lets see it will be how soon backout.. (joking!!)

Incremental GC dependent bug getting little attention from developers. Also other patches paving way for it. Sweet!!

Little progress for Removal of Trace Monkey from m-c is also done. (17k lines code removal - big code is gone say bye bye)

Object Shrink projects is also underway - which will reduce significant memory usage and lesser fragmentation.

I do not care much about all of these projects, when they come they come. I care about performance and Firefox 11 is doing that for me at least.

my god and the nightly just shot up and used 8.2GB commit charge and totally locked up my compie!!! typing this from chrome and using it for a while. the nightly, after this update is totally fried. OMG. won't even open now. gonna file a report soon.

my god and the nightly just shot up and used 8.2GB commit charge and totally locked up my compie!!! typing this from chrome and using it for a while. the nightly, after this update is totally fried. OMG. won't even open now. gonna file a report soon.

NIghtly being unstable ? What a surprise!!!!

my god and the nightly just shot up and used 8.2GB commit charge and totally locked up my compie!!! typing this from chrome and using it for a while. the nightly, after this update is totally fried. OMG. won't even open now. gonna file a report soon.

32 bit or 64 bit? Please share your changeset and addon list as well.

For CSET: about:buildconfig (copy url fro their)

Also posting about:memory info will be great help.

32 bit or 64 bit? Please share your changeset and addon list as well.

For CSET: about:buildconfig (copy url fro their)

Also posting about:memory info will be great help.

There is no way to get a process to eat 8GB of RAM on a 32bits architecture :p At least for common users.

64 bit nightly. it has never done this before.

and it goes a little somethin like this!!

I got to accuweather.com and look at comments for a news article....

I look at the facebook comments and click "view more" and poof. it suddenly spikes and locks everything up! took 2 minutes for task manager to come up.

I would look at the firefox specifics but nightly won't even load

and it won't even up the profile manager using the command:


"C:\Program Files\Nightly10\firefox.exe" -p -no-remote
[/CODE]

I can't even open it at all.

its gonna be wiped and reinstalled in order to open and I will get to that later.

64 bit nightly. it has never done this before.

and it goes a little somethin like this!!

I got to accuweather.com and look at comments for a news article....

I look at the facebook comments and click "view more" and poof. it suddenly spikes and locks everything up! took 2 minutes for task manager to come up.

I would look at the firefox specifics but nightly won't even load

and it won't even up the profile manager using the command:


"C:\Program Files\Nightly10\firefox.exe" -p -no-remote
[/CODE]

I can't even open it at all.

its gonna be wiped and reinstalled in order to open and I will get to that later.

Tried making new profile on nightly

[CODE]
"C:\Program Files\Nightly10\firefox.exe" -p "C:\Program Files\Nightly10\profile" -no-remote
[/CODE]

You better should file a bug and CC to Nicholas.

There is no way to get a process to eat 8GB of RAM on a 32bits architecture :p At least for common users.

Actually I was in rush and was in find of 32-bit or 64-bit since for the first for at in my knowledge today's update CSET for 64-bit is different than 32-bit. So it will be helpful to find a regression window.

After installing Aurora 10a2, all my add-ons have been disabled, even though I have the compatibility reporter installed & enabled. Any reason why?

Yeah, happened to me too. To fix it I went into the add-ons section of Firefox and towards the top there is a banner that says something like 'some add-ons are not compatible with FF' click enable on that banner and then restart your browser. Should be fixed.

After installing Aurora 10a2, all my add-ons have been disabled, even though I have the compatibility reporter installed & enabled. Any reason why?

Add-on Compatibility Reporter wasn't updated to disable compatibility checking for Aurora 10.

For now, you have to go into about:config, add "extensions.checkCompatibility.10.0a", set it to false, and restart Aurora.

Add-on Compatibility Reporter wasn't updated to disable compatibility checking for Aurora 10.

For now, you have to go into about:config, add "extensions.checkCompatibility.10.0a", set it to false, and restart Aurora.

I use "extensions.checkCompatibility.nightly" for the Nightly builds, and I assume it should work by changing last part to "extensions.checkCompatibility.aurora" or whatever other channel you are using. Eliminates the need to manually add a new setting in about:config every time Mozilla ups the release and no need for another unnecessary addon running for such a simple tweak.

I use "extensions.checkCompatibility.nightly" for the Nightly builds, and I assume it should work by changing last part to "extensions.checkCompatibility.aurora" or whatever other channel you are using. Eliminates the need to manually add a new setting in about:config every time Mozilla ups the release and no need for another unnecessary addon running for such a simple tweak.

No it does not. Use extensions.checkCompatibility.10.0a set to false

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now