Gmail hangs while opening a specific mail




15 years ago
14 years ago


(Reporter: dv8or70, Assigned: bugzilla)


Firefox Tracking Flags

(Not tracked)




(1 attachment)



15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10

I go to gmail and attempt to open a newly received mail. It seems that if it has
more than 5 or 6 replies to it, then when I click to open the mail, the browser
stalls. It never opens the mail page and never shows that the mail was read.
This does not occur with IE.

Reproducible: Always
Steps to Reproduce:
1. Open Gmail account
2. Open a mail thread with more than 6 replies
3. Browser will pause, Loading icon will appear, as normal.

Actual Results:  
The mail thread was never opened.

Expected Results:  
It should have opened the mail.
I can not reproduce the bug.

Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10

You might have a problem with your ISP's [transparent] proxy. Also, I noticed
that you filed with, but it only uses https during
authentication and then throws you back. 
(In reply to comment #1)
> Also, I noticed
> that you filed with, but it only uses https during
> authentication and then throws you back. 

You can choose either: just change the http to https after you are logged in,
and bookmark it. However, I can't reproduce it, either: I just opened a thread
with 94 unread messages, in a reasonable time for my connection speed.

Comment 3

14 years ago
Created attachment 165977 [details]
sample HTTP session that discovers a bug

I experience a similar problem regularly. Likewise, it works in IE but does not
in FireFox and is 100% reproducable. Here is a except of the HTTP session
recorded with LiveHttpHeaders extension, hope you'll find it helpful.
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:
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.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.