High CPU in Edge/webview2 and Chrome 130.xx VideoCaptureService processes

[BenTrojahn]

Anyone else been having problems with chromium v130 processes such as webview2  causing running away CPU consumption?   or am I again blazing new territory?  

chromium VideoCaptureService process appears to be launched at Teams start or Teams web or probably any site that wants camera access.   The process will consume and entire core+ even when the session is disconnected.  webview2 v129 does not have this issue and does not appear to spawn this separate utility process.  The process cmd are as follows.

msedgewebview2.exe" --type=utility --utility-sub-type=video_capture.mojom.VideoCaptureService
chrome.exe" --type=utility --utility-sub-type=video_capture.mojom.VideoCaptureService

2019 RDSH 
Horizon 8 2212.2
DEM 10.8 (edge and chrome are direct flex, webview2 apps are not) 
chrome, edge/webview2 are installed in base image


Since the entirety of the interwebs do not appear to have this issue, I'm leaning toward a problem with Horizon/RDS and the virtual cam and am dreading this ticket. 
 

[Philipp Siebers]

Hey,

Just a quick note on this.
I haven't been able to reproduce it with Edge v130.0.2849.80 using Horizon 8 2406 and Windows 10.

If you want to dig deeper into the issue, you could try analysing the behaviour using the Microsoft Sysinternals ProcMon tool.

[BenTrojahn]

I appreciate the reply!  Your win10 results don't surprise me.  RDSH is less common and I have found that support for issues usually take an 'interesting' path. I've been through procmon and its essentially a bunch of web cam device queries.  I now also have a ticket with Omnissa that is still in the "intentionally unhelpful" stage.  

 

Edited November 12 by BenTrojahn

[BenTrojahn]

For those keeping score at home:  Webview2 130_80 largely fixed the issues with Teams.   Chrome and Edge processes denoted by "VideoCaptureService"  are still hanging up.  Its still a big issue in our environment but its much more manageable right this moment. 

I have tickets open with MS and now Omnissa.  I noticed the delay in Webview2 releases  compared to Edge and MS said that was due to "issues that needed to be fixed"  but was surprised 130_80 appeared to help our issue.