1448631 - Firefox giving error messages on terminal.

Status: NEW

(Core :: Audio/Video: Playback, defect, P5)

Description

[kartik7239]

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

Steps to reproduce:

Opened firefox using firefox --new-window.
After some time some output is there on my terminal.


Actual results:

###!!! [Parent][DispatchAsyncMessage] Error: PClientSourceOp::Msg___delete__ Route error: message sent to unknown actor ID

[Child 4703, MediaPlayback #2] WARNING: Decoder=7f93ff2c1b60 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<mozilla::MozPromise<RefPtr<mozilla::MediaTrackDemuxer::SamplesHolder>, mozilla::MediaResult, true> > mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /build/firefox/src/mozilla-unified/dom/media/MediaDecoderStateMachine.cpp, line 3453

###!!! [Parent][DispatchAsyncMessage] Error: PClientSourceOp::Msg___delete__ Route error: message sent to unknown actor ID

[Parent 4281, Gecko_IOThread] WARNING: pipe error (65): Connection reset by peer: file /build/firefox/src/mozilla-unified/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353


Expected results:

Nothing should have been outputted to terminal.

Comment 1

[Adrian Florinescu [:aflorinescu]]

I've reproduced the exact above console error using Ubuntu 16.04 x64/Firefox 59.0.2 20180323154952,60.0b7
20180326164103, 61.0a1 20180327220126 with the following STR:

1. Open firefox from terminal.
2. Open a tab, play an youtube video.
3. Close the tab while video is playing.

I couldn't reproduce the issue on Firefox ESR 52.7.3 20180322140748 Ubuntu 16.04.

This issue seems to belong to MediaPlayback:A/V, therefore setting component for further investigation.

Note:
Bug 1438090 and bug 1390680 do seem similar, but not entirely sure if dupes.

Comment 2

[Andreas Pehrson [:pehrsons]]

I suspect we are not too bothered by these warnings. An application tries to decode something that fails so we print a warning to stderr. That seems fine.

P5 for now. jya, do you have an opinion?

If there are actual playback issues for certain machine configurations or videos we could reconsider.

Comment 3

[Jean-Yves Avenard [:jya]]

When firefox starts we check if playback works, including detection if hardware decoding is broken and so forth.

I'm unsure why this would cause such error (the media element was destroyed before the MediaDecoderStateMachine was shutdown).

:mattwoodrow was anything changed with that test recently?

Comment 4

[Matt Woodrow (:mattwoodrow)]

I don't believe anything in the test has changed recently, but I doubt automation would catch this, so it might have been erroring (for some people at least) for a while.