MediaDecoder::Invalidate() may block the main thread for up to 8 seconds

RESOLVED WORKSFORME

Status

()

P1
normal
RESOLVED WORKSFORME
2 years ago
a year ago

People

(Reporter: cpearce, Unassigned)

Tracking

(Blocks: 1 bug, {stale-bug})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qf:p1][bhr])

Attachments

(1 attachment)

(Reporter)

Description

2 years ago
Created attachment 8863984 [details]
media.txt

BHR is reporting that sometimes the main thread is blocked for up to 8 seconds while MediaDecoder::Invalidate() is on the stack.

I'll attach a list of the entry point pseudo stacks.

We have 92 reports in the reports from 29 April: https://people-mozilla.org/~mlayzell/bhr/20170429/hangs.json

I haven't dived into the causes yet.
Whiteboard: [qf:p1] → [qf:p1][bhr]
Hi Chris,
Do you know whether the reports are gathered from Nightly users or computers dedicated to tests like Try? Does it exclude the case (false positive) where the computer is busy or CPU cycles are drained by some other programs?
Flags: needinfo?(cpearce)
(Reporter)

Comment 2

2 years ago
This comes from telemetry from Nightly users. We capture the main thread stack if it's blocked for more than 8 seconds (actually, the latest reports have the threshold lowered to 125ms).

Yes, if the main thread happens to be busy for 8 seconds because the user's anti virus scanner or whatever is killing performance, we'll get hit here.

I think it would be useful to add telemetry to record how long we spend in this function; that would give us more evidence to back up the claims here.
Flags: needinfo?(cpearce)
Depends on: 1366640
No longer blocks: 1364015
Depends on: 1377025
This is a P1 bug without an assignee. 

P1 are bugs which are being worked on for the current release cycle/iteration/sprint. 

If the bug is not assigned by Monday, 28 August, the bug's priority will be reset to '--'.
Keywords: stale-bug
Flags: needinfo?(ajones)
JW - what is happening with this bug?
Flags: needinfo?(ajones) → needinfo?(jwwang)
Flags: needinfo?(ajones)
I believe bug 1377025 has fixed the issue. Per comment 2, it is possible to be a false alarm when the system is busy. I think we can close this bug and open a new one if there are new occurrences.
Flags: needinfo?(jwwang)
Status: NEW → RESOLVED
Last Resolved: a year ago
Flags: needinfo?(ajones)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.