Open Bug 1955830 Opened 5 months ago Updated 4 months ago

Firefox 136.0.2 Android property start() of MediaRecorder interface of the MediaStream Recording API error

Categories

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

Firefox 136
defect

Tracking

()

UNCONFIRMED

People

(Reporter: pwell20, Unassigned)

References

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0
Firefox for Android

Steps to reproduce:

Javascript record a live video from the html <video> element like:

const elem = document.querySelector("video");
elem.captureStream = elem.captureStream || elem.mozCaptureStream;
let stream = elem.captureStream();
let recorder = new MediaRecorder(stream);
recorder.start(); <-- error

Actual results:

Only Firefox Android version on calling recorder.start() the console is filled with:

TypeError: arguments.callee.caller.caller is null

Each of these lines containing:
value@moz-extension://a692ee57-d147-4897-b2c6-b311f49936c6/node_modules/eruda.js:2:18106
t@moz-extension://a692ee57-d147-4897-b2c6-b311f49936c6/node_modules/eruda.js:2:13271
value@moz-extension://a692ee57-d147-4897-b2c6-b311f49936c6/node_modules/eruda.js:2:33427
value/this.asyncTimer<@moz-extension://a692ee57-d147-4897-b2c6-b311f49936c6/node_modules/eruda.js:2:35061

Expected results:

That the video is being recorded as it is flawlessly and tested in
Firefox Linux 128.8.0esr (64-Bit)
Firefox Windows 136.0.2 (64-Bit)
and
Google Chrome Android Version 119.0.6045.193

The Bugbug bot thinks this bug should belong to the 'Core::Audio/Video: Playback' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Audio/Video: Playback
Product: Firefox → Core

The severity field is not set for this bug.
:jimm, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(jmathies)
Blocks: media-triage
Flags: needinfo?(jmathies)

Might have something to do with the way we play video on android. John any ideas?

Flags: needinfo?(jolin)

(In reply to Jim Mathies [:jimm] from comment #3)

Might have something to do with the way we play video on android. John any ideas?

Yes, on Android the captured stream contains SurfaceTextureImage that cannot be read back as encoder input for recording API. The ffmpeg/NDK codec efforts in bug 1934009 could be the 1st step to address this issue.

Severity: -- → S3
Depends on: 1934009
Flags: needinfo?(jolin)
Priority: -- → P3
No longer blocks: media-triage
You need to log in before you can comment on or make changes to this bug.