Closed Bug 425196 Opened 17 years ago Closed 16 years ago

AT&T Uverse Yahoo email crashes when clicking on Sender's email

Categories

(Firefox :: General, defect)

x86
Windows Vista
defect
Not set
critical

Tracking

()

VERIFIED INCOMPLETE

People

(Reporter: jeffward24, Unassigned)

References

()

Details

(Whiteboard: CLOSEME 2009-04-08)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4 Build Identifier: Firefox/3.0b4 Using AT&T UVerse service with Yahoo email, clicking on a Sender's email freezes the screen with a whitish transparency, locks up all other Firefox pages, and then shows an error stating the session crashed. I tried to do a print screen of it in my other window while typing this to you, but it crashed all of my pages, and I had to start over. I have to copy my data into Word in order to do a print screen of the crash, because this page will crash and erase data entered, even after choosing the option to "restore Previous Session" when I open another page. Reproducible: Always Steps to Reproduce: 1.Open AT&T email from http://att.my.yahoo.com 2.Click on any sender's email, either once for Preview, or double click to open. 3.Page goes transparent white, freezes all Firefox sessions, and crashes. Actual Results: All pages crash and will repeat every time. Expected Results: Firefox crashes all open pages. Open the sender's email.
can you reproduce this unconfirmed problem using newest firefox 3.x or 3.1 beta? http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: CLOSEME 2009-04-08
@Reporter, we have not heard back from you in a while, so I am closing this bug as INCOMPLETE. You can reopen this bug if more information becomes available. Some helpful information you can provide us is found at http://quality.mozilla.org/bug-writing-guidelines. You should also use a recent version of Firefox, from http://www.getfirefox.com.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.