Open Bug 707321 Opened 14 years ago Updated 3 years ago

Intermittent browser_581593.js | an unexpected uncaught JS exception reported through window.onerror - Script error. at :0

Categories

(Firefox :: Session Restore, defect, P3)

x86
macOS
defect

Tracking

()

Tracking Status
firefox11 --- fixed

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [parts of test disabled])

Attachments

(1 file)

https://tbpl.mozilla.org/php/getParsedLog.php?id=7713910&tree=Mozilla-Inbound Rev3 MacOSX Leopard 10.5.8 mozilla-inbound debug test mochitest-other on 2011-12-02 13:04:54 PST for push fb802350a2d2 TEST-PASS | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser/browser_581593.js | JSON.parse succeeded ++DOMWINDOW == 25 (0x2a91c398) [serial = 3017] [outer = 0x2a4aa730] WARNING: NS_ENSURE_TRUE(mMutable) failed: file /builds/slave/m-in-osx-dbg/build/netwerk/base/src/nsSimpleURI.cpp, line 292 WARNING: NS_ENSURE_SUCCESS(rv, false) failed with result 0x8000FFFF: file /builds/slave/m-in-osx-dbg/build/content/base/src/nsContentUtils.cpp, line 2579 WARNING: NS_ENSURE_TRUE(pusher.Push(aBoundElement)) failed: file /builds/slave/m-in-osx-dbg/build/content/xbl/src/nsXBLProtoImplMethod.cpp, line 355 WARNING: Not same origin error!: file /builds/slave/m-in-osx-dbg/build/dom/base/nsJSEnvironment.cpp, line 340 TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser/browser_581593.js | an unexpected uncaught JS exception reported through window.onerror - Script error. at :0 Stack trace: JS frame :: chrome://mochikit/content/tests/SimpleTest/SimpleTest.js :: simpletestOnerror :: line 964 native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0 JavaScript error: chrome://browser/content/aboutSessionRestore.js, line 277: attempt to run compile-and-go script on a cleared scope JavaScript error: chrome://browser/content/aboutSessionRestore.js, line 277: attempt to run compile-and-go script on a cleared scope WARNING: Not same origin error!: file /builds/slave/m-in-osx-dbg/build/dom/base/nsJSEnvironment.cpp, line 340 TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser/browser_581593.js | an unexpected uncaught JS exception reported through window.onerror - Script error. at :0 Stack trace: JS frame :: chrome://mochikit/content/tests/SimpleTest/SimpleTest.js :: simpletestOnerror :: line 964 native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0 INFO TEST-END | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser/browser_581593.js | finished in 547ms
Attached patch Patch v0.1 — — Splinter Review
This just ignores the error. I think we should land this and file a followup, a la bug 706730. There's actually a root issue here which I've half tracked down, already filed as bug 691255.
Assignee: nobody → paul
Attachment #579848 - Flags: review?(dietrich)
Comment on attachment 579848 [details] [diff] [review] Patch v0.1 Review of attachment 579848 [details] [diff] [review]: ----------------------------------------------------------------- i don't understand. why not leave it as-is and set dependency on that root cause bug?
Comment on attachment 579848 [details] [diff] [review] Patch v0.1 Review of attachment 579848 [details] [diff] [review]: ----------------------------------------------------------------- see comment #46
Attachment #579848 - Flags: review?(dietrich) → review-
(In reply to Dietrich Ayala (:dietrich) from comment #46) > Comment on attachment 579848 [details] [diff] [review] > Patch v0.1 > > Review of attachment 579848 [details] [diff] [review]: > ----------------------------------------------------------------- > > i don't understand. why not leave it as-is and set dependency on that root > cause bug? Because it wouldn't really hurt anybody & instead we're getting 10+ oranges a day, soon to be double that if we don't figure out the problem before the next merge. We're already doing this for the backslashsplosion test (bug 706730), as well as a bunch of other tests (https://mxr.mozilla.org/mozilla-central/ident?i=ignoreAllUncaughtExceptions)
Blocks: 709913
(In reply to Dietrich Ayala (:dietrich) from comment #46) > i don't understand. why not leave it as-is and set dependency on that root > cause bug? Because leaving it as is, with the constant grinding tiresome nuisance of having to look at this goddamn stupid useless orange twenty or thirty times a day will make me get sick of it, and disable the whole test.
Comment on attachment 579848 [details] [diff] [review] Patch v0.1 Review of attachment 579848 [details] [diff] [review]: ----------------------------------------------------------------- better than endless orange.
Attachment #579848 - Flags: review- → review+
Comment on attachment 579848 [details] [diff] [review] Patch v0.1 [Approval Request Comment] Regression caused by (bug #): User impact if declined: none Testing completed (on m-c, etc.): m-c Risk to taking this patch (and alternatives if risky): none This is a test-only change and should have no impact on aurora (except that there will be fewer orange tests)
Attachment #579848 - Flags: approval-mozilla-aurora?
Comment on attachment 579848 [details] [diff] [review] Patch v0.1 [Triage Comment] Test change only - approved for aurora.
Attachment #579848 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Assignee: paul → nobody
(Whiteboard not quite true, but close enough and matches existing search queries)
Whiteboard: [orange] → [orange][parts of test disabled]
Whiteboard: [orange][parts of test disabled] → [parts of test disabled]
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: