Closed Bug 789709 Opened 12 years ago Closed 12 years ago

Intermittent browser_600545.js | an unexpected uncaught JS exception reported through window.onerror - NS_ERROR_FAILURE: Failure at chrome://browser/content/browser.js:4533

Categories

(Firefox :: Session Restore, defect)

Product:
Firefox
Component:
Session Restore
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure) 

https://tbpl.mozilla.org/php/getParsedLog.php?id=15074098&tree=Ionmonkey
Rev3 WINNT 6.1 ionmonkey pgo test mochitest-other on 2012-09-08 06:47:35 PDT for push 18142c3076a1
slave: talos-r3-w7-077

TEST-START | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js
TEST-INFO | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js | Console message: [JavaScript Error: "TelemetryStopwatch: key "FX_SESSION_RESTORE_COLLECT_DATA_MS" was already initialized" {file: "resource://gre/modules/TelemetryStopwatch.jsm" line: 53}]
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js | an unexpected uncaught JS exception reported through window.onerror - NS_ERROR_FAILURE: Failure at chrome://browser/content/browser.js:4533
Stack trace:
    JS frame :: chrome://mochikit/content/tests/SimpleTest/SimpleTest.js :: simpletestOnerror :: line 980
    native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0

TEST-INFO | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js | Console message: [JavaScript Error: "NS_ERROR_FAILURE: Failure" {file: "chrome://browser/content/browser.js" line: 4533}]
I think that's the same failure as bug 789102 and will be fixed by it.
Status: NEW → ASSIGNED
QA Contact: ttaubert
Marking as fixed by bug 794436.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.