[Branch] Firefox 2.0.0.8 fixlist (NOW RELEASED)

Discussion about official Mozilla Firefox builds
chob
Posts: 4283
Joined: May 17th, 2003, 12:05 pm
Location: London, UK

Post by chob »

Aureliano Buendía wrote:I have this crash:
http://talkback-public.mozilla.org/sear ... B36831607G
(step to reproduce: goto the site reported and click on one of plays)

Mozilla/5.0 (Windows; U; Windows NT 5.1; it; rv:1.8.1.8) Gecko/20071008 Firefox/2.0.0.8 ID:2007100816

Looks like a crash in real-player; do you have the latest official (non-beta) version installed?
User avatar
[:Aureliano Buendía]
Posts: 323
Joined: August 12th, 2006, 5:50 am
Location: Italy

Post by [:Aureliano Buendía] »

Hi chob.
I dont have real-player installed: FF should be warning for this and not directly crash... or not?
Ciao
chob
Posts: 4283
Joined: May 17th, 2003, 12:05 pm
Location: London, UK

Post by chob »

Aureliano, firefox should never crash no matter what ;) But from your talkback stack, you are crashing in nppl3260.dll and afaik that is the RealPlayer(tm) G2 LiveConnect-Enabled Plug-In (32-bit). Please can you do about:plugins in the URL bar, hit enter, and see if there are any Real Player entries, and if so, any version numbers that go along with them?
User avatar
Stifu
Posts: 984
Joined: July 13th, 2007, 8:02 am

Post by Stifu »

I tried earlier with Firefox 2.0.0.7 and the latest Real Player. No crash, but the whole screen (or actually, both of my screens) would go black for a second, as I started or left videos...
User avatar
[:Aureliano Buendía]
Posts: 323
Joined: August 12th, 2006, 5:50 am
Location: Italy

Post by [:Aureliano Buendía] »

chob wrote:...see if there are any Real Player entries, and if so, any version numbers that go along with them?

See here al my real player plugins:
Image
chob
Posts: 4283
Joined: May 17th, 2003, 12:05 pm
Location: London, UK

Post by chob »

Aureliano Buendía wrote:
chob wrote:...see if there are any Real Player entries, and if so, any version numbers that go along with them?

See here al my real player plugins:
Image

Yeah, looks like you need to update your real player plugins to start with.
User avatar
[:Aureliano Buendía]
Posts: 323
Joined: August 12th, 2006, 5:50 am
Location: Italy

Post by [:Aureliano Buendía] »

Thanks chob.
I download and install "Real Alternative Light" (only plugin for browser): now my plugins version is 6.0.12.1739 and the application not crash.

Ciao
LetsSurf
Posts: 37
Joined: May 3rd, 2004, 10:22 am

Post by LetsSurf »

david5717 wrote:I got the following error, I don't yet know if it's due to anything in this build:

[Exception... "Component is not available" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: file : ///lbuild/firefox/components/nsSessionStore.js :: sss_saveState :: line 1749" data: no]
[Break on this error] oState.session = { state: ((this._loadState == STATE_RUNNING) ? STATE_RUNNIN...

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.8) Gecko/20071008 Firefox/2.0.0.8 ID:2007100816


I also get this problem since the latest beta upgrade. I'm not sure what's at fault the build or maybe a plugin.

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.8.1.8) Gecko/20071008 Firefox/2.0.0.8 ID:2007100816
chob
Posts: 4283
Joined: May 17th, 2003, 12:05 pm
Location: London, UK

Post by chob »

LetsSurf wrote:
david5717 wrote:I got the following error, I don't yet know if it's due to anything in this build:

[Exception... "Component is not available" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: file : ///lbuild/firefox/components/nsSessionStore.js :: sss_saveState :: line 1749" data: no]
[Break on this error] oState.session = { state: ((this._loadState == STATE_RUNNING) ? STATE_RUNNIN...

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.8) Gecko/20071008 Firefox/2.0.0.8 ID:2007100816


I also get this problem since the latest beta upgrade. I'm not sure what's at fault the build or maybe a plugin.

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.8.1.8) Gecko/20071008 Firefox/2.0.0.8 ID:2007100816

When do you both get this error message? eg: what triggers it?
Is it reproducable if you make a new firefox profile for a test?
- http://kb.mozillazine.org/Profile_manager
(Do not delete your existing profile ;))
LetsSurf
Posts: 37
Joined: May 3rd, 2004, 10:22 am

Post by LetsSurf »

Very strangely I can't reproduce the error any more. So maybe best to ignore. It doesn't do it with a fresh profile, I can't even get it todo it with my old profile now. But it seemed to do it every time the session would save, e.g on successful page load.

chob wrote:
LetsSurf wrote:
david5717 wrote:I got the following error, I don't yet know if it's due to anything in this build:

[Exception... "Component is not available" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: file : ///lbuild/firefox/components/nsSessionStore.js :: sss_saveState :: line 1749" data: no]
[Break on this error] oState.session = { state: ((this._loadState == STATE_RUNNING) ? STATE_RUNNIN...

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.8) Gecko/20071008 Firefox/2.0.0.8 ID:2007100816


I also get this problem since the latest beta upgrade. I'm not sure what's at fault the build or maybe a plugin.

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.8.1.8) Gecko/20071008 Firefox/2.0.0.8 ID:2007100816

When do you both get this error message? eg: what triggers it?
Is it reproducable if you make a new firefox profile for a test?
- http://kb.mozillazine.org/Profile_manager
(Do not delete your existing profile ;))
david5717
Posts: 301
Joined: July 18th, 2003, 7:39 am
Location: Baton Rouge, LA, USA

Post by david5717 »

chob wrote:
LetsSurf wrote:
david5717 wrote:I got the following error, I don't yet know if it's due to anything in this build:

[Exception... "Component is not available" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: file : ///lbuild/firefox/components/nsSessionStore.js :: sss_saveState :: line 1749" data: no]
[Break on this error] oState.session = { state: ((this._loadState == STATE_RUNNING) ? STATE_RUNNIN...

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.8) Gecko/20071008 Firefox/2.0.0.8 ID:2007100816


I also get this problem since the latest beta upgrade. I'm not sure what's at fault the build or maybe a plugin.

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.8.1.8) Gecko/20071008 Firefox/2.0.0.8 ID:2007100816

When do you both get this error message? eg: what triggers it?
Is it reproducable if you make a new firefox profile for a test?
- http://kb.mozillazine.org/Profile_manager
(Do not delete your existing profile ;))


I haven't noticed it since, but I'll keep my eyes open and if I encounter it again I'll do my best to find a debug-friendly reproduction procedure.
rickst29
Posts: 182
Joined: January 22nd, 2003, 10:45 pm

Post by rickst29 »

I've been running 'Bon Echo' nightlies since late Friday evening, in regular usage. (Not a defined test.) I haven't run into any new problems (Linux, obviously). I still experience 100% CPU from time to time, not related to the Windows bug (which occurs only upon a network connection disruption). It may be related to flaky layout code, which is already being re-engineered in a big way in Gran Paradiso, so I'm not gonna worry about it. Or it may be related to my huge number of RIPs, some of which may not be defined real well. Or other mess-ups within in my HUGE number of add-ons.

Bottom line is, some things seem slightly better, NOTHING seems worse. As best as I can tell, it's ready. I've got Tab-Mix-Plus running, maybe this protects me from the Session Store STATE_RUNNING test Break? But I have told TMP to let me use the Firefox built in Session Manager, not it's own, so I should be getting the problem if it's still present in Saturday's and Sunday's "Bon Echo" Nightlies. I did make a couple of intentional crashes "just for fun", and the Session's Tabs were restored-- SessionStore data *is* getting saved OK on my box.

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.8pre) Gecko/20071014 BonEcho/2.0.0.8pre - Build ID: 2007101403

BTW, has the "BonEcho" I'm using gone too far past the 2.0.0.8 "Release Candidates" to be of use in "verifying 2.0.0.8"? And if so, WHY is it still be called a 2.0.0.8 (errrr, if it's already <u>ahead</u> of what's being planned for Release tomorrow, then it should already be wearing the designation "2.0.0.9pre", right?) Either nothing's happened since RC2 (and Bon Echo == RC2, even though it nags me to update each night); or Bon Echo *is not* a 2.0.0.8 test build, and it needs a Revision Bump to stop confusing dummies such as me. [Or, and this possibility worries me: Bon Echo *is* the test build, RC2 isn't up to date, but because Bon Echo hasn't been copied as the RC no one else has been testing it. EEK!!!]

Yeah, I am easily confused and not to bright-- please clue me in. :)
Make a fire FOR a man, he'll be warm for the rest of the night. Set a man ON fire, he'll be warm for the rest of his life!
pal-moz
Posts: 5937
Joined: September 23rd, 2005, 5:40 pm
Location: Tokyo , Japan

Post by pal-moz »

@rickst29

official 2.0.0.8 is not out yet, so Nightly is called/named 2.0.0.8pre.
if official will be out, Nightly will be bumped to 2.0.0.9pre.
rickst29
Posts: 182
Joined: January 22nd, 2003, 10:45 pm

Thanks, pal

Post by rickst29 »

I would have created a separate Branch when the RC was cut (and pushed Bon Echo to 2.0.0.9pre right then). I have no idea how many non-2.0.0.8 Updates I'm now running. I'll back down to 2.0.0.8 when it's Released. By running Bon Echo, I've gone PAST the 2.0.0.8 plan, right?

If Bon Echo really *is* the 2.0.0.8 tree, and the Release Candidates are just old versions which went through a bit more testing, then mozilla.org needs to get the word out-- test with Bon Echo, if you want to test the _latest_ Candidate Build. (Maybe the word is out and I'm the only person who hasn't heard , :lol:). But their sure are lots of 1008 (RC2) Build ID's making an appearance in this Thread, so either I'm not testing the 2.0.0.8 pre-release -- or they're not testing the newest "pre-RC" Builds.

Either way, it's confusing (IMO), and I used to do this stuff for a living. Is <u>everything</u> in Bon Echo planned for 2.0.0.8, or is there an un-announced and un-organized "branch/2.0.x tree" split already present? If Bon-Echo *is* the "RC3 candidates", maybe it should be linked inside the FTP site-- within the 2.0.0.8 Folder, along with the Rc1 and RC2 Folders, link Bon Echo Nightly as "Nightly RC3 Candidates".
Make a fire FOR a man, he'll be warm for the rest of the night. Set a man ON fire, he'll be warm for the rest of his life!
Tolien
Posts: 206
Joined: October 26th, 2005, 4:16 pm

Post by Tolien »

Everything that happens in Bon Echo will make it into a 2.0.0.x release.
Right now, the 1.8 branch (tinderbox) is "restricted" - the only checkins going into the branch right now should be for 2.0.0.8. An RC's just a specific hourly (and a nightly is just a special case of an hourly) that's been built with the official branding switched on.

Although you're getting a new nightly every 24 hours with a different build ID, odds are nothing has actually changed, and the difference between the latest RC and branch nightly should be minimal as well.

That's my understanding at least - if I'm wrong, I expect I'll get corrected soon enough :)
Post Reply