1407553 - Frequent media mochitests timeouts on Windows 10

Status: NEW

(Core :: Audio/Video: cubeb, defect, P3)

Description

[JW Wang [:jwwang] [:jw_wang]]

https://treeherder.mozilla.org/logviewer.html#?job_id=135854322&repo=try&lineNumber=8935

04:13:18     INFO -  GECKO(9348) | [Child 3508, MediaPlayback #2] WARNING: 2580598c220 StateCallback, mState=STARTED cubeb_state=STARTED: file z:/build/build/src/dom/media/AudioStream.cpp, line 711
04:13:18     INFO -  GECKO(9348) | [Child 3508, MediaPlayback #4] WARNING: 2580598c040 StateCallback, mState=STARTED cubeb_state=STARTED: file z:/build/build/src/dom/media/AudioStream.cpp, line 711
04:13:18     INFO -  GECKO(9348) | [Child 3508, Unnamed thread 25807b2b000] WARNING: 2580598c040 StateCallback, mState=STARTED cubeb_state=DRAINED: file z:/build/build/src/dom/media/AudioStream.cpp, line 711
04:13:18     INFO -  GECKO(9348) | [Child 3508, MediaPlayback #2] WARNING: 2580598c040 StateCallback, mState=DRAINED cubeb_state=STOPPED: file z:/build/build/src/dom/media/AudioStream.cpp, line 711
04:13:19     INFO -  GECKO(9348) | [Child 3508, Unnamed thread 258063f5400] WARNING: 2580598c220 StateCallback, mState=STARTED cubeb_state=DRAINED: file z:/build/build/src/dom/media/AudioStream.cpp, line 711
04:13:19     INFO -  GECKO(9348) | [Child 3508, MediaPlayback #2] WARNING: 2580598c220 StateCallback, mState=DRAINED cubeb_state=STOPPED: file z:/build/build/src/dom/media/AudioStream.cpp, line 711
04:13:21     INFO -  GECKO(9348) | [Child 3508, MediaPlayback #4] WARNING: 25805970b50 StateCallback, mState=STARTED cubeb_state=STARTED: file z:/build/build/src/dom/media/AudioStream.cpp, line 711
04:13:21     INFO -  GECKO(9348) | [Child 3508, MediaPlayback #3] WARNING: 2580598e7a0 StateCallback, mState=STARTED cubeb_state=STARTED: file z:/build/build/src/dom/media/AudioStream.cpp, line 711


My logs show that stream 25805970b50 and 2580598e7a0 didn't get cubeb_state=DRAINED and therefore playback couldn't reach the end. That is the reason why we have many test timeouts on Windows 10 recently.

Comment 1

[JW Wang [:jwwang] [:jw_wang]]

Hi Kinetik,
Per comment 0, can you find someone to look at the cubeb issue? Thanks!

Comment 2

[Matthew Gregan [:kinetik]]

> That is the reason why we have many test timeouts on Windows 10 recently.

What range do you mean by "recently"?  There haven't been many changes to the Windows libcubeb backend for several months IIRC.

Comment 3

[JW Wang [:jwwang] [:jw_wang]]

Within one week, there have been several bugs opened or reopened for media test timeout.

Comment 4

[Matthew Gregan [:kinetik]]

Thanks.  It's possible but unlikely (because it should only affect capture and/or full-duplex streams AFAIK) that bug 1405258 is implicated, padenot can confirm.  There aren't any other recent changes to the libcubeb Windows audio backend (cubeb_wasapi.cpp hasn't changed since early Sept), which would tend to suggest the issue lies elsewhere.

Comment 5

[Paul Adenot (:padenot)]

(In reply to Matthew Gregan [:kinetik] from comment #4)
> Thanks.  It's possible but unlikely (because it should only affect capture
> and/or full-duplex streams AFAIK) that bug 1405258 is implicated, padenot
> can confirm.  There aren't any other recent changes to the libcubeb Windows
> audio backend (cubeb_wasapi.cpp hasn't changed since early Sept), which
> would tend to suggest the issue lies elsewhere.

I agree. I don't see this being the root cause.

Comment 6

[Blake Wu [:bwu][:blakewu]]

It looks this problem impacts so many test cases. 
Is anyone working on this?

Comment 7

[Blake Wu [:bwu][:blakewu]]

Chunmin,
Per discussion, please check why we got so many test failures on Windows 10.
Thanks!

Comment 8

[C.M.Chang[:chunmin]]

Sure. I will check this ASAP.