Closed Bug 1296961 Opened 8 years ago Closed 8 years ago

Intermittent devtools/client/netmonitor/test/browser_net_statistics-02.js | Uncaught exception - at chrome://mochitests/content/browser/devtools/client/netmonitor/test/browser_net_statistics-02.js:34 - Error: cross-process JS call failed

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox50 --- affected
firefox51 --- affected

People

(Reporter: aryx, Unassigned)

References

Details

(Keywords: intermittent-failure, regression) 

https://treeherder.mozilla.org/logviewer.html#?job_id=34356565&repo=mozilla-inbound

This has been intermittent for the last two weeks. First occurrences after retriggering the OSX 10.10 debug M(dt5) job: https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=d8a125a7dc496d5366d4065cc58938da5145d41c&filter-searchStr=10.10%20debug%20M-e10s(dt5)

11:20:12     INFO -  22 INFO TEST-PASS | devtools/client/netmonitor/test/browser_net_statistics-02.js | Request to reconfigure the tab was recorded. -
11:20:12     INFO -  23 INFO Console message: [JavaScript Error: "no element found" {file: "http://example.com/browser/devtools/client/netmonitor/test/sjs_content-type-test-server.sjs?sts=304&fmt=xml" line: 1}]
11:20:12     INFO -  24 INFO Netork monitor pane shown successfully.
11:20:12     INFO -  25 INFO Starting test...
11:20:12     INFO -  26 INFO TEST-PASS | devtools/client/netmonitor/test/browser_net_statistics-02.js | The initial frontend mode is correct. -
11:20:12     INFO -  27 INFO Displaying statistics view
11:20:12     INFO -  28 INFO Console message: [JavaScript Error: "no element found" {file: "http://example.com/browser/devtools/client/netmonitor/test/sjs_content-type-test-server.sjs?sts=304&fmt=xml" line: 1}]
11:20:12     INFO -  29 INFO TEST-PASS | devtools/client/netmonitor/test/browser_net_statistics-02.js | The frontend mode is currently in the statistics view. -
11:20:12     INFO -  30 INFO Reloading page
11:20:12     INFO -  31 INFO TEST-UNEXPECTED-FAIL | devtools/client/netmonitor/test/browser_net_statistics-02.js | Uncaught exception - at chrome://mochitests/content/browser/devtools/client/netmonitor/test/browser_net_statistics-02.js:34 - Error: cross-process JS call failed
11:20:12     INFO -  Stack trace:
11:20:12     INFO -      @chrome://mochitests/content/browser/devtools/client/netmonitor/test/browser_net_statistics-02.js:34:3
11:20:12     INFO -      Tester_execTest@chrome://mochikit/content/browser-test.js:791:9
11:20:12     INFO -      Tester.prototype.nextTest</<@chrome://mochikit/content/browser-test.js:711:7
11:20:12     INFO -      SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:741:59
11:20:12     INFO -      Tester_execTest@chrome://mochikit/content/browser-test.js:791:9
11:20:12     INFO -      Tester.prototype.nextTest</<@chrome://mochikit/content/browser-test.js:711:7
11:20:12     INFO -      SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<@chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:741:59
Terrence, can you take a look at this, please? Treeherder doesn't show earlier failures (went back 4 days in the history).
Flags: needinfo?(terrence)
That's very, very strange. The patch that's implicated adds a very specific assertion to HeapSlot::set. The crashes in the linked runs are nowhere near HeapSlot::set. I don't see how the patch in question could have caused any writes to memory, so I think downstream effects are out. Hurm...
Okay, some retriggers on the previous push also returned this error.
Flags: needinfo?(terrence)
This only hit a couple times in late August. Various ObjectIsMarkedGray assertion fixes have landed since, so I'm going to call this WFM.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
This is still hitting on Beta50, unfortunately :(
status-firefox50: --- → affected
You need to log in before you can comment on or make changes to this bug.