675727 - FF 5.x crashes - everytime - when on Yahoo! Mail web site. Safari or Chrome doesn't

Status: RESOLVED WORKSFORME

(Core :: JavaScript Engine, defect)

Description

[Arvind]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:5.0.1) Gecko/20100101 Firefox/5.0.1
Build ID: 20110707182747

Steps to reproduce:

Visited Yahoo! Mail web site


Actual results:


After few clicks on different e-mails, the FF crashes


Expected results:


Should not crash :-)

The fact that the same site works ok with Safari and Chrome, on the same Mac OS X (Lion) - tells me that its not the Web site issue.

Comment 1

[Matthias Versen [:Matti]]

A crash is always a bug in the client and not the website.
You get a real crash and not a hang/freeze ?

Please post a crash ID of the crash if you get a crash, follow this instructions to get the crash ID.
https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report

Comment 2

[Vlad [QA]]

WFM on Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:8.0a1) Gecko/20110802 Firefox/8.0a1 
No crashes in yahoo mail beta.

Comment 3

[Vlad [QA]]

Reporter, please try to see if this is reproducible on the latest Firefox beta:
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/6.0b5/mac/en-US/
Thanks

Comment 4

[Arvind]

Here is the CrashID:  bp-1af004a9-a5bb-4452-8f25-e197d2110809

Will try on the FF beta

Arvind

Comment 5

[David Mandelin [:dmandelin]]

(In reply to Arvind from comment #4)
> Here is the CrashID:  bp-1af004a9-a5bb-4452-8f25-e197d2110809
> 
> Will try on the FF beta
> 
> Arvind

How does it work in the beta?

Comment 6

[Arvind]

Just started using it for past two days.  Let me put some mileage on it and I will update the bug info.

Comment 7

[Arvind]

Okay... so here is the update: (Short and sweet)

 It works !

Have been using the 6.0 beta for around a week now and have been hitting the same URLs which were crashing the FF-5.x. No crashes.

So thank you for fixing the issue in FF-6.0 !

Let me know the process to close this bug.

Arvind

Comment 8

[Thomas Ahlblom]

Considering comment 7, and that we don't know exactly what fixed it, resolving as WORKSFORME.