Closed
Bug 1272856
Opened 9 years ago
Closed 9 years ago
Intermittent e10s browser_originattributes.js | Uncaught exception - at :0 - Error: operation not possible on dead CPOW
Categories
(Core :: General, defect, P5)
Core
General
Tracking
()
RESOLVED
FIXED
mozilla52
People
(Reporter: philor, Assigned: jhao)
References
(Blocks 1 open bug)
Details
(Keywords: intermittent-failure, Whiteboard: [OA-testing])
Attachments
(1 file)
|
2.48 KB,
patch
|
ehsan.akhgari
:
review+
|
Details | Diff | Splinter Review |
Comment 1•9 years ago
|
||
This is a general issue, not networking/cookie related.
There should be an umbrella bug for all of the intermittents with the "Error: operation not possible on dead CPOW" failure.
Component: Networking: Cookies → General
Updated•9 years ago
|
Blocks: e10s-tests
tracking-e10s:
--- → +
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Updated•9 years ago
|
status-firefox49:
--- → affected
status-firefox50:
--- → affected
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 16•9 years ago
|
||
Jonathan, this is showing up as one of the more frequent dead CPOW oranges being hit in automation. Can you please take a look?
TEST-UNEXPECTED-FAIL | netwerk/cookie/test/browser/browser_originattributes.js | Uncaught exception - at resource://gre/modules/RemoteAddonsParent.jsm:880 - Error: operation not possible on dead CPOW
Stack trace:
getContentDocument@resource://gre/modules/RemoteAddonsParent.jsm:880:3
RemoteBrowserElementInterposition.getters.contentDocument@resource://gre/modules/RemoteAddonsParent.jsm:897:10
AddonInterpositionService.prototype.interposeProperty/desc.get@resource://gre/components/multiprocessShims.js:165:38
getCookiesFromTitle@chrome://mochitests/content/browser/netwerk/cookie/test/browser/browser_originattributes.js:105:7
checkCookies@chrome://mochitests/content/browser/netwerk/cookie/test/browser/browser_originattributes.js:72:35
Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:937:23
this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:816:7
Promise*this.PromiseWalker.scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:747:11
this.PromiseWalker.schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:779:7
this.PromiseWalker.completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:714:7
receiveMessage@resource://testing-common/ContentTask.jsm:113:9
Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:937:23
this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:816:7
Promise*this.PromiseWalker.scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:747:11
this.PromiseWalker.schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:779:7
this.PromiseWalker.completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:714:7
Tester_execTest@chrome://mochikit/content/browser-test.js:784:9
Tester.prototype.nextTest</<@chrome://mochikit/content/browser-test.js:704:7
SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:741:59
| Assignee | ||
Comment 17•9 years ago
|
||
The exception happens when we tried to get browser.contentDocument. I got rid of it since we can get return values from ContentTask.spawn directly.
Ehsan, please review this. Thanks.
Attachment #8790636 -
Flags: review?(ehsan)
| Assignee | ||
Updated•9 years ago
|
Flags: needinfo?(jhao)
| Assignee | ||
Updated•9 years ago
|
Whiteboard: [OA-testing]
| Assignee | ||
Updated•9 years ago
|
Assignee: nobody → jhao
| Assignee | ||
Updated•9 years ago
|
Status: NEW → ASSIGNED
Updated•9 years ago
|
Attachment #8790636 -
Flags: review?(ehsan) → review+
| Assignee | ||
Comment 18•9 years ago
|
||
| Assignee | ||
Updated•9 years ago
|
Keywords: checkin-needed
Comment 19•9 years ago
|
||
Pushed by cbook@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/d457b93de5b7
Fix intermittent e10s browser_originattributes.js r=ehsan
Keywords: checkin-needed
Comment 20•9 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox52:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla52
Comment 21•9 years ago
|
||
| bugherder uplift | ||
Flags: in-testsuite+
Comment 22•9 years ago
|
||
| bugherder uplift | ||
You need to log in
before you can comment on or make changes to this bug.
Description
•