+++ This bug was initially created as a clone of Bug #1207785 +++ It would appear bug 1207785 has introduced the #1 most verbose warning during testing. > 6773 [NNNNN] WARNING: Could not parse plugin domain!: file dom/base/nsObjectLoadingContent.cpp, line 1497 This warning [1] shows up in the following test suites: > mozilla-central_ubuntu32_vm-debug_test-reftest-e10s-1-bm07-tests1-linux32-build2.txt:1755 > mozilla-central_ubuntu32_vm-debug_test-reftest-1-bm07-tests1-linux32-build2.txt:1748 > mozilla-central_ubuntu32_vm-debug_test-reftest-e10s-2-bm08-tests1-linux32-build3.txt:1264 > mozilla-central_ubuntu32_vm-debug_test-reftest-3-bm05-tests1-linux32-build99.txt:1256 > mozilla-central_ubuntu32_vm-debug_test-mochitest-e10s-browser-chrome-1-bm07-tests1-linux32-build2.txt:139 > mozilla-central_ubuntu32_vm-debug_test-mochitest-browser-chrome-1-bm01-tests1-linux32-build142.txt:135 > mozilla-central_ubuntu32_vm-debug_test-mochitest-3-bm02-tests1-linux32-build194.txt:62 > mozilla-central_ubuntu32_vm-debug_test-mochitest-2-bm02-tests1-linux32-build226.txt:54 > mozilla-central_ubuntu32_vm-debug_test-mochitest-1-bm03-tests1-linux32-build123.txt:54 > mozilla-central_ubuntu32_vm-debug_test-mochitest-other-bm07-tests1-linux32-build3.txt:53 > mozilla-central_ubuntu32_vm-debug_test-crashtest-bm05-tests1-linux32-build100.txt:52 > mozilla-central_ubuntu32_vm-debug_test-crashtest-e10s-bm06-tests1-linux32-build28.txt:50 > mozilla-central_ubuntu32_vm-debug_test-mochitest-e10s-2-bm07-tests1-linux32-build2.txt:47 > mozilla-central_ubuntu32_vm-debug_test-mochitest-5-bm06-tests1-linux32-build144.txt:26 > mozilla-central_ubuntu32_vm-debug_test-mochitest-e10s-1-bm02-tests1-linux32-build178.txt:20 > mozilla-central_ubuntu32_vm-debug_test-web-platform-tests-3-bm08-tests1-linux32-build1.txt:18 > mozilla-central_ubuntu32_vm-debug_test-web-platform-tests-6-bm06-tests1-linux32-build39.txt:9 > mozilla-central_ubuntu32_vm-debug_test-reftest-4-bm05-tests1-linux32-build102.txt:8 > mozilla-central_ubuntu32_vm-debug_test-reftest-2-bm08-tests1-linux32-build0.txt:7 > mozilla-central_ubuntu32_vm-debug_test-web-platform-tests-5-bm06-tests1-linux32-build43.txt:6 > mozilla-central_ubuntu32_vm-debug_test-mochitest-browser-chrome-7-bm08-tests1-linux32-build1.txt:3 > mozilla-central_ubuntu32_vm-debug_test-web-platform-tests-reftests-bm01-tests1-linux32-build30.txt:2 > mozilla-central_ubuntu32_vm-debug_test-web-platform-tests-8-bm02-tests1-linux32-build27.txt:1 > mozilla-central_ubuntu32_vm-debug_test-web-platform-tests-4-bm06-tests1-linux32-build46.txt:1 > mozilla-central_ubuntu32_vm-debug_test-mochitest-e10s-browser-chrome-7-bm04-tests1-linux32-build20.txt:1 > mozilla-central_ubuntu32_vm-debug_test-mochitest-e10s-5-bm08-tests1-linux32-build0.txt:1 > mozilla-central_ubuntu32_vm-debug_test-mochitest-browser-chrome-3-bm08-tests1-linux32-build0.txt:1 It shows up in 265 tests. A few of the most prevalent: > 160 - file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/svg/as-image/img-widthAndHeight-slice-2.html > 160 - file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/svg/as-image/img-widthAndHeight-slice-1.html > 160 - file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/svg/as-image/img-widthAndHeight-meet-2.html > 160 - file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/svg/as-image/img-widthAndHeight-meet-1.html > 160 - file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/svg/as-image/img-width-slice-2.html > 160 - file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/svg/as-image/img-width-slice-1.html > 160 - file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/svg/as-image/img-width-meet-2.html > 160 - file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/svg/as-image/img-width-meet-1.html > 160 - file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/svg/as-image/img-novb-widthAndHeight-meet-1-em.html > 160 - file:///builds/slave/test/build/tests/reftest/tests/layout/reftests/svg/as-image/img-novb-width-meet-1.html [1] https://hg.mozilla.org/mozilla-central/annotate/5f16c6c2b969f70e8da10ee34853246d593af412/dom/base/nsObjectLoadingContent.cpp#l1497

Comment on attachment 8669260 [details] [diff] [review] Patch 1 (v1) - Remove domain parsing warning message from youtube embed telemetry probe code Review of attachment 8669260 [details] [diff] [review]: ----------------------------------------------------------------- LGTM Kyle, do you know why we are unable to parse the "plugin domain"? Could this error path affect end users and not just our test machines?

We will need to uplift this fix to Aurora 43 because bug 1207785 was uplifted too.

All the referenced tests are using data URIs, which it trips up on. That's fine, and expected. I'll disable the warning for now, and file a followup to see if there's a better way to deal with this.

Comment on attachment 8669260 [details] [diff] [review] Patch 1 (v1) - Remove domain parsing warning message from youtube embed telemetry probe code Approval Request Comment [Feature/regressing bug #]: New feature. [User impact if declined]: Can't track amount of youtube embeds seen [Describe test coverage new/current, TreeHerder]: Seeing it come up fine on telemtry dashboard [Risks and why]: None [String/UUID change made/needed]: None

Comment on attachment 8669260 [details] [diff] [review] Patch 1 (v1) - Remove domain parsing warning message from youtube embed telemetry probe code OK, approved for aurora uplift