Media Remoting trying to start for a desktop mirroring session. |
||
Issue description
Chrome Version: 71.0.3550.0
OS: Mac OS X 10_13_6
This bug is being created from a single user feedback report. A brief triage happened over email, Yuri took a quick look noting that there's an issue here.
Internal feedback ID: 85657206049
[2018-09-12 14:08:09.51][SEVERE][mr.mirror.cast.Session] Media Remoting start failed: Failed to parse tab ID from source:
urn:x-org.chromium.media:source:desktop
Failed to parse tab ID from source:
urn:x-org.chromium.media:source:desktop
Error: Failed to parse tab ID from source:
urn:x-org.chromium.media:source:desktop
at chrome-extension://pkedcjkdefgpdelpbcmbmeomcjbeemfm/mirroring_cast_streaming.js:671:13
at chrome-extension://pkedcjkdefgpdelpbcmbmeomcjbeemfm/mirroring_cast_streaming.js:351:35
,
Sep 17
Investigated: Nothing bad is actually happening, just some error logging. The root cause is that code internal to the Media Router Component extension is preparing the Media Remoting subsystem for use, and that subsystem can't start because it can't identify a tab. That's just fine. Note that no code is trying to switch out of mirroring and over to a remoting session. The error logs are referring to the start of the subsystem, not a session. As this is not a Chromium issue, closing as WontFix. Also, I double-checked that this is not a problem in the upcoming Chromium C++ replacement for the extension code (in src/components/mirroring). |
||
►
Sign in to add a comment |
||
Comment 1 by m...@chromium.org
, Sep 17Owner: m...@chromium.org
Status: Started (was: Untriaged)