New issue
Advanced search Search tips

Issue 856774 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 20
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Cast very often requires restarting chrome for it to work

Project Member Reported by azilio@google.com, Jun 26 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Have Chrome opened for a while... After using cast a bunch of times too.
2. Try casting a tab or a youtube video page

What is the expected behavior?
My cast devices are shown.

What went wrong?
No cast devices are shown. I can cast fine from my phone instead.
If I restart Chrome browser the devices then show up.

Did this work before? N/A 

Is it a problem with Flash or HTML5? N/A

Does this work in other browsers? N/A

Chrome version: 67.0.3396.87  Channel: n/a
OS Version: OS X 10.13.3
Flash Version: 

Contents of chrome://gpu:
 
Components: -Internals>Media Internals>Cast

Comment 2 by mfo...@chromium.org, Jun 26 2018

Labels: Needs-Feedback
We recently fixed some bugs that prevented a component that supports Cast from getting into a bad state. However it's possible this is due to other factors like our mDNS discovery getting into bad state.  We know this happens sometimes on Mac.

Can you do following things next time this happens:

1. open chrome://media-router-internals in a new tab and copy into this bug

2. open chrome://net-internals/#capture in a new tab and click "include actual bytes received", then open the Cast dialog and wait until it times out

3. Click on "events" on the same page, enter ":5353" in the filter box, press enter, and then select all matching entries in the table

4. copy-paste the JSON contents in the right hand side into a file and attach it here

Thanks!




Labels: Needs-Triage-M67
Status: WontFix (was: Unconfirmed)
Closing due to inactivity. Feel free to reopen if the issue is still there. Follow instructions on #2 for the reopen.

Sign in to add a comment