1433031 - Firefox 60.0 - sound stop working after a while

Status: RESOLVED INCOMPLETE

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

Description

[drJeckyll]

Attachment: about:support -> Media

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20180124220129

Steps to reproduce:

Run Firefox 60.0a1 (2018-01-24) (64-bit) on Gentoo Linux with asound.

In console I get:
[DEBUG SHUTDOWN] Register: decoder=0x7ff2ab805200, count=6
[DEBUG SHUTDOWN] Register: decoder=0x7ff2b1bc3a00, count=7
[DEBUG SHUTDOWN] Register: decoder=0x7ff2b1c8ae00, count=8
[DEBUG SHUTDOWN] Register: decoder=0x7ff2b1c3a200, count=9
[DEBUG SHUTDOWN] Register: decoder=0x7ff2b1d96200, count=10
[DEBUG SHUTDOWN] Register: decoder=0x7ff2b1bc4400, count=11
[DEBUG SHUTDOWN] Register: decoder=0x7ff2b1bc9e00, count=12
[DEBUG SHUTDOWN] Register: decoder=0x7ff2b2958600, count=13
[DEBUG SHUTDOWN] Register: decoder=0x7ff2b1c90200, count=14
[DEBUG SHUTDOWN] Register: decoder=0x7ff2b2952e00, count=15
[DEBUG SHUTDOWN] Register: decoder=0x7ff2b2ca7c00, count=16
[DEBUG SHUTDOWN] Register: decoder=0x7ff2b1c8ea00, count=17
[DEBUG SHUTDOWN] Register: decoder=0x7ff2b3593c00, count=18
[DEBUG SHUTDOWN] Register: decoder=0x7ff2c2d04400, count=19
[DEBUG SHUTDOWN] Register: decoder=0x7ff2b31c6800, count=20
[DEBUG SHUTDOWN] Register: decoder=0x7ff2b351bc00, count=21
[DEBUG SHUTDOWN] Register: decoder=0x7ff2b2ca2e00, count=22
[DEBUG SHUTDOWN] Register: decoder=0x7ff2c45e2e00, count=23

every time sound is played, instead of:
[DEBUG SHUTDOWN] Register: decoder=0x7ff2ad876400, count=1
[DEBUG SHUTDOWN] ShutdownDecoder: decoder: 'ffmpeg audio decoder' (0x7ff2c3759900) flush:1
[DEBUG SHUTDOWN] operator(): pool=0x7ff2bbfa68b0 shutdown=false count=0
[DEBUG SHUTDOWN] Shutdown: decoder=0x7ff2ad876400 state machine=0x7ff2bbd8b800
[DEBUG SHUTDOWN] Enter: state machine=0x7ff2ab8fac10 reader=0x7ff2b1b4fa60

which I is displayed when sound is played normally.


Actual results:

Sound stop working, and there is no indication on the tab (sound icon). 

If I try to play youtube video for example it never start to play. It may be different issue however.


Expected results:

Sound never stop to work.

Comment 1

[Andreas Pehrson [:pehrsons]]

"asound" is alsa? Our default builds only support pulseaudio.

Apart from that it looks a bit like bug 1426679. Audio remoting could be at play here.

Comment 2

[Matthew Gregan [:kinetik]]

It looks like this is using ALSA via the apulse wrapper (https://github.com/i-rinat/apulse), since the sink/source names shown in about:support are unique to https://github.com/i-rinat/apulse/blob/master/src/apulse-context.c#L160.

Best thing to do would be to try to reproduce with a complete and working PulseAudio install.

Comment 3

[drJeckyll]

(In reply to Andreas Pehrson [:pehrsons] from comment #1)
> "asound" is alsa? Our default builds only support pulseaudio.
> 
> Apart from that it looks a bit like bug 1426679. Audio remoting could be at
> play here.

apulse it's called - sorry for the mistake. It's visible from the screenshot that is not ALSA - I give up of compiling and now just use Nightly which use pulse audio.

Comment 4

[drJeckyll]

(In reply to Andreas Pehrson [:pehrsons] from comment #1)
> "asound" is alsa? Our default builds only support pulseaudio.
> 
> Apart from that it looks a bit like bug 1426679. Audio remoting could be at
> play here.

Sorry for another bug, but I don't think it is the same as bug 1426679. It was working until the day I filled the bug with FF 59 and now 60. So it was OK before that and when audio stop I fill the bug in the same day.

Comment 5

[Andreas Pehrson [:pehrsons]]

In that case, could you try running mozregression [1] to figure out which commit regressed this?

You filed this yesterday when Nightly was 60. Do you know if the version you were on before that update (when it worked) was 60 or 59?

[1] http://mozilla.github.io/mozregression/

Comment 6

[drJeckyll]

(In reply to Andreas Pehrson [:pehrsons] from comment #5)
> In that case, could you try running mozregression [1] to figure out which
> commit regressed this?
> 
> You filed this yesterday when Nightly was 60. Do you know if the version you
> were on before that update (when it worked) was 60 or 59?
> 
> [1] http://mozilla.github.io/mozregression/

I can but it not happened today very fast and will take some time. 

My firefox get updated automatically every day I think, so it must be previous day build.

Comment 7

[Andreas Pehrson [:pehrsons]]

(In reply to drJeckyll from comment #6)
> My firefox get updated automatically every day I think, so it must be
> previous day build.

Ok. Mozregression will let you know for sure.

Comment 8

[drJeckyll]

How can I run mozregression with apulse? I try to copy apulse folder (from /lib) under (mozregression)/venv/lib but no audio is detected.

Comment 9

[Andreas Pehrson [:pehrsons]]

Mozregression is a tool (the UI version preferred) that will download different versions of Nightly, with the user reporting success or failure after a manual test for each version.

You set the initial range from a version you know work until one you know doesn't and the tool will essentially do a binary search until it has found the, or at least minimized a range of, commits that caused the regression.

Comment 10

[drJeckyll]

(In reply to Andreas Pehrson [:pehrsons] from comment #9)
> Mozregression is a tool (the UI version preferred) that will download
> different versions of Nightly, with the user reporting success or failure
> after a manual test for each version.
> 
> You set the initial range from a version you know work until one you know
> doesn't and the tool will essentially do a binary search until it has found
> the, or at least minimized a range of, commits that caused the regression.

I know that already and have to run mozregression for another bug, couple of days ago. 

What I ask is how to run it with apulse support, because sound is not detected that way. It seems that mozregression use some kind of virtual environment (it has bin, lib, include inside), but when I put apulse folder which on system is located under /lib, Firefox not detect these libraries inside which are part of apulse (pulse audio replacement for system without PA).

Comment 11

[Andreas Pehrson [:pehrsons]]

(In reply to drJeckyll from comment #10)
> I know that already and have to run mozregression for another bug, couple of
> days ago. 
> 
> What I ask is how to run it with apulse support, because sound is not
> detected that way. It seems that mozregression use some kind of virtual
> environment (it has bin, lib, include inside), but when I put apulse folder
> which on system is located under /lib, Firefox not detect these libraries
> inside which are part of apulse (pulse audio replacement for system without
> PA).

Ah, sorry.

I don't have any advice for that I'm afraid.

Comment 12

[Randell Jesup [:jesup] (needinfo me)]

You can manually do mozregression by downloading from archive.mozilla.org and bisecting.  If you want to go into a single day, it's possible to download builds from mozilla-central landings or inbound landings

Comment 13

[drJeckyll]

In recent days (build) my sound never stop. I guess it's fixed or it was something which was broken for a short time. 

May be we can close the this ticket.

Comment 14

[Nils Ohlmeier [:drno]]

Closing as requested. Feel free to re-open any time if the problem should come back.