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

Issue 737068 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
ossu@chromium.org
solenberg@chromium.org
█ olka@chromium.org
maxmorin@chromium.org
grunell@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Distinguish between the first missed callback and all the others in Media.Audio.Capture.DetectedMissingCallbacks

Project Member Reported by olka@chromium.org, Jun 27 2017 
Now we log only boolean value. However, there is a difference in both route causes and user experience depending on if it's the first callback timed out (may be related to stream startup issues, user has not got any audio at all) or one of the later callbacks (may be related to performance issues, user has been receiving audio for some period of time).

Would be helpful to log "no callbacks missed/first callback missed/later callback missed".
Project Member

Comment 1 by sheriffbot@chromium.org, Jun 27 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by kwiberg@chromium.org, Jun 28 2018

Owner: olka@chromium.org
Status: Assigned (was: Untriaged)
Olga, should this one be closed?

Comment 3 by olka@chromium.org, Jun 28 2018

Owner: ----
Status: Available (was: Assigned)
I'd still like to have that when we get back to tackling glitches.
►

Sign in to add a comment