crash when i close a tab in which imdb.com is opened

RESOLVED INVALID

Status

()

--
critical
RESOLVED INVALID
9 years ago
9 years ago

People

(Reporter: s_a_u_p_h, Unassigned)

Tracking

({crash})

3.0 Branch
x86
Windows XP
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.19) Gecko/2010031422 Firefox/3.0.19 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.19) Gecko/2010031422 Firefox/3.0.19 (.NET CLR 3.5.30729)

In the browser I have some tabs opened, in each tabs I have opened some sites. In one of the tabs I have open this site: http://www.imdb.com/
for example (http://www.imdb.com/title/tt0361862/). If i want to close this tab, the browser crashes. I have to reopen it again. The occurrence is systematic: every time when I want to close a tab in which I have opened www.imdb.com it crashes! And this happened only for this site.

Reproducible: Always

Steps to Reproduce:
1.in the browser I have some tabs opened, in each tabs I have opened some sites. In one of the tabs I have opened this site: http://www.imdb.com/ for example (http://www.imdb.com/title/tt0361862/).
2. If i want to close this tab, the browser crashes. If I want to close other tabs (but not this), firefox doesn't crash.
3.
Actual Results:  
Every time when I want to close a tab in which www.imdb.com is opened, firefox crashes

Expected Results:  
When the tab with the specified site is closed, firefox should not crash.
(Reporter)

Updated

9 years ago
Keywords: crash
Fiurefox 3.0 is no longer supported. There are known crashes in it. Please upgrade to Firefox 3.6.3, then report back if you still get the crash. If you still get it, give a stracktrace. https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report
Severity: normal → critical
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
Version: unspecified → 3.0 Branch
You need to log in before you can comment on or make changes to this bug.