Open Bug 1784738 Opened 2 years ago Updated 2 years ago

if the broadcaster is doing an audio only broadcast at DokiDoki LIVE the video won't load

Categories

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

Firefox 103
x86_64
Windows 10
defect

Tracking

()

People

(Reporter: Motouyuu1, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0

Steps to reproduce:

Go to: https://www.doki.live/691420359

Actual results:

The audio doesn't load

Expected results:

The audio should load up and you can year the person talking

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

This page seems to act like the page on bug 1783778 - increasing memory use, blocked autoplay.

See Also: → 1783778

Hi Konally, thanks for the report!

I was able to reproduce the bug on Linux with autoplay disabled. Do you have autoplay disabled? If so, could you please try the following:

  1. Visit about:preferences in the URL bar, or click the hamburger button and click settings.
  2. Type "autoplay" into the search box in the settings window.
  3. Click the settings button for Autoplay.
  4. Change the default for all websites to "Allow Audio and Video".
  5. Navigate to https://www.doki.live/691420359

Does the audio playback work for you now?

If so, you may be able to go back into the settings menu as per above and set the default back to "Block Audio and Video" and then whitelist doki.live. I was unable to directly whitelist doki.live from the link provided, as Firefox would go very slow when I attempted to load the page with autoplay disabled. Instead, the following worked for me:

  1. Revisit the autoplay settings as per the previous instructions, but set the default for all websites to "Block Audio and Video".
  2. Navigate to https://doki.live/download (This page doesn't doesn't cause Firefox to slow down in my testing)
  3. Click on the lock icon in the URL bar.
  4. Click on the "connection secure" button that appears.
  5. Click on "More information".
  6. Click the "Permissions" tab.
  7. Uncheck the "Use Default" box under "Autoplay".
  8. Click "Allow audio and video".
  9. Try visiting https://www.doki.live/691420359

Can you give this a try and report back with your results? Please also post your about:support page information to help diagnose the bug further.

Flags: needinfo?(Motouyuu1)

Just chiming in to say that I had the same behavior re: memory usage / autoplay events in bug 1783778 as per Asif.

Status: UNCONFIRMED → NEW
Ever confirmed: true

Hi, I have Autoplay settings set to Allow and Video so it plays automatically

Flags: needinfo?(Motouyuu1)

It doesn't work. I've even done many new installations in the past and the same thing happens, it won't play. I haven't upgraded to Windows 11 yet, though. I always have Autoplay set to Allow Audio and Video by default

See Also: → 1785041

(In reply to Konally from comment #7)

https://www.doki.live/999999
https://www.doki.live/817064862
https://www.doki.live/87601432
https://www.doki.live/311716048

Quickly check those they are broadcasting right now

Thanks Konally!

OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64

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

For more information, please visit auto_nag documentation.

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

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

For more information, please visit auto_nag documentation.

Flags: needinfo?(jmathies)
Flags: needinfo?(jmathies) → needinfo?(azebrowski)

Hi Konally, I took another look at this on the latest nightly, and am no longer able to reproduce the issue with or without autoplay blocked. I do get a flood of autoplay-related events like the following:

[Child 1066051: Main Thread]: D/nsMediaElement PlayPromise 7f0eb4fdc680 rejected with 0x806e0002 (NotAllowedErr)                                                                                                    
[Child 1066051: Main Thread]: D/nsMediaElement 7f0eb641e800 SetMuted(1) called by JS                                                                                                                                
[Child 1066051: Main Thread]: D/nsMediaElement 7f0eb641e800 SetVolume(0.000000) called by JS                                                                                                                        
[Child 1066051: Main Thread]: D/nsMediaElement 7f0eb641e800 Play() called by JS readyState=4                                                                                                                        
[Child 1066051: Main Thread]: D/nsMediaElement 7f0eb641e800 created PlayPromise 7f0eb4fdc940                                                                                                                        
[Child 1066051: Main Thread]: D/nsMediaElement PlayPromise 7f0eb4fdc940 rejected with 0x806e0002 (NotAllowedErr)                                                                                                    
[Child 1066051: Main Thread]: D/nsMediaElement 7f0eb641e800 SetMuted(1) called by JS                                                                                                                                
[Child 1066051: Main Thread]: D/nsMediaElement 7f0eb641e800 SetVolume(0.000000) called by JS                                                                                                                        
[Child 1066051: Main Thread]: D/nsMediaElement 7f0eb641e800 Play() called by JS readyState=4                                                                                                                        
[Child 1066051: Main Thread]: D/nsMediaElement 7f0eb641e800 created PlayPromise 7f0eb4fdca40                                                                                                                        
[Child 1066051: Main Thread]: D/nsMediaElement PlayPromise 7f0eb4fdca40 rejected with 0x806e0002 (NotAllowedErr)                                                                                                    
...

I did also see a malformed XML error in the console:

XML Parsing Error: not well-formed
Location: https://www.doki.live/api/live/nav/
Line Number 1, Column 1:

Would you be able to see if the latest nightly fixes playback for you?

Flags: needinfo?(azebrowski) → needinfo?(Motouyuu1)
Severity: -- → S3

It still occurs with Nightly 106.0a1

Flags: needinfo?(Motouyuu1)

Hi Konally! I haven't been able to reproduce this but would like to investigate further. The below steps can generate a profile/logging information that should help narrow things down.

  • Download an updated Firefox Nightly build as you did earlier (https://www.mozilla.org/en/firefox/all/#product-desktop-nightly. You can simply decompress it and run it directly. It will not share a profile with your main Firefox installation, and the directory can simply be deleted afterwards)
  • Navigate to https://profiler.firefox.com, click the button to enable the profiler button, and select the preset called "Media"
  • Open a new tab, navigate to about:networking, click on the Logging tab on the left, and paste in MediaDecoder:5,MediaFormatReader:5,MediaDecoderStateMachine:5,PlatformDecoderModule:5,Autoplay:5,nsMediaElementEvents:5,nsMediaElement:5 in the box Current Log Modules
  • Click the button Set log modules
  • Start a profile by clicking the down arrow next to the profiler icon that has been added to your toolbar (upper-right, should look like a dial), selecting the Media profiler preset, and pressing "start recording"
  • Reproduce the issue.
  • After having reproduced, click the profiler button again to end profiling, and capture the profile
  • After some time, this will open a new tab with the Firefox Profiler interface, click share on the top-right, make sure to include hidden threads (it's enabled by default), and share the URL here (or privately at <azebrowski@mozilla.com>, there is a way to download the profile, to e.g. attach it to an email).

Here's a screencast that shows the procedure (modulo the log modules name to put in the text box, that are different) https://paul.cx/public/cubeb-logging.webm, it's just a bit longer than a minute and doesn't require other software apart from Firefox Nightly. Thank you!

Flags: needinfo?(Motouyuu1)

https://share.firefox.dev/3sf1GZS

I am a little shocked that you could not reproduce the issue because I was on Windows 10 for a long time when it started happening. I have now moved to Windows 11 with a brand new installation and I went to https://www.doki.live/ and clicked on an Audio only broadcast (The audio only broadcasts are the ones with the yellow volume graphic by the number of people in the room) and it just stays in a loading loop. This is on a brand new install of Windows 11; no upgrade from Windows 10 a new fresh installation. I opened the same link in Brave and Edge and it loads up. I also used the Nightly as you asked and it does the same thing.

Flags: needinfo?(Motouyuu1)

Thanks Konally, I'm able to repro now and will investigate further.

No longer blocks: media-triage
You need to log in before you can comment on or make changes to this bug.