New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 876892 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 885256
Owner:
Closed: Sep 21
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

[Video Capture Service] Removing virtual device does not update device list in UI

Project Member Reported by chfremer@chromium.org, Aug 22

Issue description

Virtual device is removed by closing the message pipe of a corresponding mojom.VirtualDevice or mojom.Producer from the client side. This should update the list of devices that the service enumerates. However, potentially due to caching at the level of https://cs.chromium.org/chromium/src/content/browser/renderer_host/media/media_devices_manager.h?q=MediaDevicesManager&dr=CSs&l=46, the change to the device list does not get propagated to the UI/Renderer.

A solution probably has to involve an event being sent out from the service to trigger a cache update, similar to when a physical device is plugged in or unplugged.

 
Cc: weigua@chromium.org bmayer@chromium.org
Labels: M-70
Cc: z...@chromium.org
Labels: -Pri-2 Pri-1
Raising to P1 because otherwise there is no chance this is going to be looked at before M70 branches.
It looks like at least on Linux this does not seem to be an issue.
I added a test case, and it passes on my local Linux workstation. 

https://chromium-review.googlesource.com/c/chromium/src/+/1188966

It might be that the caching for enumerating devices is not active on Linux. Will check on other platforms as well.
It looks like, currently, only Windows and Mac fail the test, which is consistent with the device monitoring being enabled by default only on these two platforms, see https://cs.chromium.org/chromium/src/content/public/common/content_features.cc?l=231&gsn=kMediaDevicesSystemMonitorCache.

That is assuming there are no Finch experiments where the monitoring is rolled out on other platforms.

We still need to solve this eventually, but for M69/M70 on ChromeOS we might be okay for now.
Cc: chfremer@chromium.org
 Issue 870356  has been merged into this issue.
Should we bump this to M71?
Labels: -M-70 M-71
Yes. Didn't make the cut.
Mergedinto: 885256
Status: Duplicate (was: Assigned)
This should resolve itself once Bug 885256 is fixed.

Sign in to add a comment