Closed Bug 811873 Opened 12 years ago Closed 12 years ago

WebRTC crashtests for mozRTCPeerConnection fail when 'browser.tabs.remote' set to true

Categories

(Core :: WebRTC, defect, P1)

19 Branch
defect

Tracking

()

RESOLVED FIXED
mozilla20

People

(Reporter: whimboo, Assigned: whimboo)

References

()

Details

(Whiteboard: [getUserMedia][blocking-gum+][qa-])

Attachments

(1 file)

The following crashtest fails for Linux opt builds when they run the Cipc (Crashtest IPC) tests:

REFTEST TEST-UNEXPECTED-FAIL | file:///home/cltbld/talos-slave/test/build/reftest/tests/dom/media/tests/crashtests/791330.html | load failed: timed out waiting for reftest-wait to be removed

The only reason why this can happen is when the onSuccess callback is not excuted for the getUserMedia call.

Ted, do you know how we can execute those tests? Or at least who is responsible for this testrun?
We are also failing in '801227.html' now:

reftest/tests/dom/media/tests/crashtests/801227.html | load failed: timed out waiting for reftest-wait to be removed

I will figure out how to run those tests on Thursday, so we can get it investigated.
Summary: 'crashtests/791330.html' times out for Cipc tests on Linux opt → 'crashtests/791330.html' and 'crashtests/801227.html' time out for Cipc tests on Linux opt
Priority: -- → P1
Whiteboard: [getUserMedia], [blocking-gum+]
Sorry, meant to comment on this earlier. If you look at the full log of any test run you can always find the command used to execute the test suite. For Cipc it's this:
python reftest/runreftest.py --appname=firefox/firefox-bin --utility-path=bin --extra-profile-file=bin/plugins --symbols-path=http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-linux/1353465869/firefox-20.0a1.en-US.linux-i686.crashreporter-symbols.zip --setpref=browser.tabs.remote=true reftest/tests/testing/crashtest/crashtests.list

So the only difference from normal crashtest is the "--setpref=browser.tabs.remote=true" line.
That's what Randell tried but wasn't successful in it. I will check that now.
Ok, I can reproduce this problem also on OS X now with a profile created by the reftest framework. 'browser.tabs.remote=true' doesn't seem to be the single cause here. I will analyze the profile now what specific setting or extension is causing that.
OS: Linux → All
Hardware: x86 → All
An exception gets thrown:

[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [IPeerConnection.initialize]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: jar:file:///Applications/Firefox/Nightly.app/Contents/MacOS/omni.ja!/components/PeerConnection.js :: PeerConnection.prototype._queueOrRun :: line 262"  data: no]

http://mxr.mozilla.org/mozilla-central/source/dom/media/PeerConnection.js#262

261     if (!this._pending) {
262       obj.func.apply(this, obj.args);
263       if (obj.wait) {
Whiteboard: [getUserMedia], [blocking-gum+] → [getUserMedia][blocking-gum+][automation-blocked]
Depends on: 814527
All tests which make use of the mozRTCPeerConnection will be affected. So this is indeed a core issue and not a test failure. We have to wait for a fix on bug 814527 now.
Summary: 'crashtests/791330.html' and 'crashtests/801227.html' time out for Cipc tests on Linux opt → WebRTC crashtests for mozRTCPeerConnection fail when 'browser.tabs.remote' set to true
Blocks: 814531
We can disable Cipc tests by just adding the following line to the crashtest list:

+skip-if(browserIsRemote) include ../../dom/media/tests/crashtests/crashtests.list

I propose that we disable all WebRTC tests for remote browsers right now. I don't think it's worth setting the flag on a case by case basis. Once we are good with those tests and multiple processes we can re-enable them.
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Attachment #686274 - Flags: review?(rjesup)
Comment on attachment 686274 [details] [diff] [review]
Disable crashtest-ipc

Review of attachment 686274 [details] [diff] [review]:
-----------------------------------------------------------------

r+; I assume you intend it to still be disabled for all tests, not just Cipc
Attachment #686274 - Flags: review?(rjesup) → review+
(In reply to Randell Jesup [:jesup] from comment #9)
> r+; I assume you intend it to still be disabled for all tests, not just Cipc

The line in the crashtest.list file is still commented out, which is the all tests case. Keep in mind that the next merge of m-c to alder will cause a conflict here.
https://hg.mozilla.org/mozilla-central/rev/ea84c06a3b38
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla20
Whiteboard: [getUserMedia][blocking-gum+][automation-blocked] → [getUserMedia][blocking-gum+][automation-blocked][qa-]
Flags: in-testsuite+
Whiteboard: [getUserMedia][blocking-gum+][automation-blocked][qa-] → [getUserMedia][blocking-gum+][qa-]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: