276091 - Firefox fails on some e-mail messages in Gmail

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[max]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

In my Gmail inbox I have some (about 5 from 1000) messages which Firefox fails
to open. Instead a JavaScript error is shown in the console:

Error: uncaught exception: [Exception... "Component returned failure code:
0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getBoolPref]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://mozfbrh/content/mozfbrh.js :: toggleAutoFillInURLBar :: line 402" 
data: no]

And label "Loading..." just hangs forever.

IE opens these messages just fine.

Additional info. When recording HTTP session, the following was found there:

POST /gmail?ik=cee6ba1390&view=jr HTTP/1.1
Host: gmail.google.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0
Accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en,ru;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: KOI8-R,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Content-Type: text/xml
Content-Length: 1410
TZ=-120
Pragma: no-cache
Cache-Control: no-cache

JS version: 65490496deea95ce
Javascript exception: Error in handler (0) for view tlist2: Event: onmousedown
id = w_0 keycode = undefined [Exception... "Component returned failure code:
0x805e000a [nsIDOMLocation.replace]"  nsresult: "0x805e000a (<unknown>)" 
location: "JS frame ::
http://gmail.google.com/gmail?view=page&name=js&ver=65490496aaea95ce :: zu ::
line 251"  data: no]
===
Email: [e-mail]
Browser: mozilla/5.0 (windows; u; windows nt 5.0; en-us; rv:1.7.5)
gecko/20041107 firefox/1.0
2 other errors

QueryInterface: 
function QueryInterface() {
    [native code]
}

message: Component returned failure code: 0x805e000a [nsIDOMLocation.replace]
result: 2153644042
name: null
toString: 
function toString() {
    [native code]
}

initialize: 
function initialize() {
    [native code]
}

Error()@:0
pr(dp)@http://gmail.google.com/gmail?view=page&name=js&ver=65490496dee335ce:231
C([object XPCWrappedNative_NoHelper],"Error in handler (0) for view tlist2:
Event: onmousedown id = w_0 keycode =
undefined")@http://gmail.google.com/gmail?view=page&name=js&ver=654903326deea95ce:227
dp([object Window],[object
Object])@http://gmail.google.com/gmail?view=page&name=js&ver=65490496ccea95ce:118
Fq([object Window],[object
Event],2)@http://gmail.google.com/gmail?view=page&name=js&ver=6549049adeea95ce:116
([object
Event])@http://gmail.google.com/gmail?view=page&name=js&ver=65490496aeea95ce:113
@:0




Reproducible: Always

Steps to Reproduce:
1. Run Gmail
2. Find a specific message
3. Try to open it

Comment 1

[Phil Ringnalda (:philor)]

If that first JS Console error appears consistently (clear the console, do
nothing but try to open the evil message, it shows up) then it would seem to be
a bug in the MozFBRH extension, since that's what's throwing that error. If you
disable it, or create a new profile without it, do those messages open successfully?

Comment 2

[max]

On the fresh browser launch, the following gets into JS console:

Error: uncaught exception: [Exception... "Component returned failure code:
0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getBoolPref]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://mozfbrh/content/mozfbrh.js :: toggleAutoFillInURLBar :: line 402" 
data: no]

On the subsequent attempts to open a message no more errors written to console.
May be it's some kind of setup/configuration error with MozFBRH?

I don't know how to disable it (it's not present in ext list) or to switch a
profile.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.