New issue
Advanced search Search tips

Issue 754765 link

Starred by 1 user
Status: Assigned
Owner:
emir...@chromium.org
Cc:
chfremer@chromium.org
guidou@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Investigate edge cases for detecting active video capture in renderer

Project Member Reported by emir...@chromium.org, Aug 11 2017 
In the below CL, we add counters to track the number of active media streams in a renderer tab, so that process won't be backgrounded when a session is on. Increment logic is tied to Start(). However, the decrement logic is tied to multiple elements: Error(), Ended(), Stop(). We should cover the scenarios where they overlap
https://chromium-review.googlesource.com/c/609032

Comment 1 by emir...@chromium.org, Aug 22 2017 

I think we should limit these actions to Start() and Stop() coming from renderer side. We can ignore the Error() and Ended() states coming from camera when deciding the tab priority, i.e. it is OK to avoid backgrounding the tab that has a camera error because it will still send balck frames via peer connection.

Comment 2 by emir...@chromium.org, Aug 22 2017

Labels: Hotlist-GoodFirstBug
Adding GoodFirstbug label re MediaStreams and WebRTC.
►

Sign in to add a comment