Issue metadata
Sign in to add a comment
|
chrome.tabCapture.capture doesn't work randomly
Reported by
evo...@gmail.com,
Jul 13
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.59 Safari/537.36 Steps to reproduce the problem: 1. Install https://chrome.google.com/webstore/detail/kakeffogmhndegdafnbobknemagiikak extension 2. Open some live video on twitch or youtube 3. Try to change audio volume on a tab with installed extension What is the expected behavior? No error should happen each time. What went wrong? Often getting error "Unchecked runtime.lastError: Could not start audio source" when trying to call chrome.tabCapture.capture with parameter {audio: !0, video: !1}. When it works fine then you can see cast icon on the tab and no errors in console. Did this work before? Yes I believe it was working every time in v67. Then after some update in beta version it started to give this error randomly. Does this work in other browsers? N/A Chrome version: 69.0.3489.0 Channel: canary OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Sometimes it works and volume is regulated correctly (and can be boosted, for which I'm using it myself). But often this error happens and you will need to restart the browser to try again.
,
Jul 13
And here is slightly changed version which shows errors in console.
,
Jul 13
,
Jul 13
,
Jul 13
evolgr@ Thanks for the issue. Tested this issue on Windows 10 on the reported version 69.0.3489.0 and unable to reproduce the issue by following the below steps. 1. Launched Chrome and added the extension in comment #2 in chrome://extensions. 2. Played a video on youtube.com and opened devtools -> console. 3. Changed the volume on the installed extension and cannot observe any error on the Console. Attached is the screen cast for reference. Request you to retry the issue on a new chrome profile and update the thread with the observations. Thanks..
,
Jul 13
susan.boorgula@ Thanks for trying to reproduce the issue. How many times did you try to do it? Because as I said sometimes it works just fine until you restart the browser and try again. Today I was able to reproduce it with the 2nd try (on 1st try all was fine). Here is the video:
,
Jul 13
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 16
Unable to reproduce this issue on latest chrome 69.0.3492.0 using Windows 7 & 10 and Mac 10.13.5. Attaching screen-cast for reference. Note: Tested this issue five times unable to reproduce from our end. @Reporter: Requesting you to please upgrade to latest chrome 69.0.3492.0 .Could you please upgrade to latest chrome 69.0.3492.0, you can download latest chrome builds here:" https://www.chromium.org/getting-involved/dev-channel ". Let us know if issue still persists or not. Thanks!
,
Jul 16
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 16
Wasn't able to reproduce it in 69.0.3486.0 (Official Build) dev (64-bit) in "Ubuntu 18.04 LTS" VM (tried 20 times). So it may be Windows only bug.
,
Jul 17
As per comment#6 and comment#9, as the issue is not reproducible at TE end, adding 'TE-NeedsTriageHelp' label and requesting the appropriate team to look into the issue and help in further triaging. Note: Removing Needs-Bisect label to it and feel free to add if required. Thanks.! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by evo...@gmail.com
, Jul 13