Closed
Bug 670576
Opened 13 years ago
Closed 13 years ago
Firefox crashes while clicking on a closed window object in web-console
Categories
(DevTools :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 646184
People
(Reporter: seitz.christoph, Unassigned)
Details
Crash Data
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0 Build ID: 20110615151330 Steps to reproduce: 1) Open the web-console in the developer menu. 2) Open a window via " window.open("http://www.mozilla.org/"); 3) Close the Window 4) Click on the returned window object Actual results: Firefox crashes and the bug reporter starts. Expected results: Either a information should be shown with the null object or an error message should be shown that the object ist null
Comment 1•13 years ago
|
||
I get that crash on 5, but I can't reproduce on Beta, Aurora or Nightly, so this was apparently fixed a while ago.
Comment 2•13 years ago
|
||
This looks like bug 646184.
Comment 3•13 years ago
|
||
I can reproduce the crash on Firefox 5 but not on Nightly (didn't test other versions). https://crash-stats.mozilla.com/report/index/bp-3bf779bf-7384-400b-9abe-65aa32110710 https://crash-stats.mozilla.com/report/index/bp-42c7d85a-a947-4d24-a94d-fbccf2110710 The testcase of bug 646184 crashes as well: https://crash-stats.mozilla.com/report/index/bp-227aca08-ad64-4975-825e-57dcc2110711 BTW, [@ nsGlobalWindow::GetLocalStorage(nsIDOMStorage**) ] should be added to this bug's (and maybe bug 646184's) Summary and Crash Signature field, so that it is shown on crash-stats and found in searches. (I would change it myself, but I don't have the rights to change it...)
Comment 4•13 years ago
|
||
Bug 646184 has a target milestone of Firefox 6, which corroborates our findings.
Updated•13 years ago
|
Crash Signature: [@ nsGlobalWindow::GetLocalStorage(nsIDOMStorage**) ]
Updated•13 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•