Closed Bug 1785177 Opened 3 years ago Closed 2 years ago

Disabling Autoplay causes constant CPU usage and increases RAM usage on TikTok

Categories

(Web Compatibility :: Site Reports, defect)

Firefox 104
x86_64
Windows 10
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: alamalo.exe, Unassigned)

References

Details

Attachments

(1 file)

Attached image console.png

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

Steps to reproduce:

  1. Block Audio and Video Autoplay
  2. Got to: https://www.tiktok.com/@redbull/video/7097593801274969350
  3. Don't click anywhere

Actual results:

Video won't start playing but CPU and RAM usage continues to increase until you click anywhere on the page and video starts playing.

I see 2 warnings using the console repeated thousands of times:
"Autoplay is only allowed when approved by the user, the site is activated by the user, or media is muted."
"[xgplayer] >>>>playPromise.catch NotAllowedError"

Expected results:

Video should be blocked from playing but CPU and RAM usage shouldn't be affected by this.

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
See Also: → 1785041
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)

I'm able to reproduce this. Guessing it's something the site is doing.

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

Blocks: media-triage
Severity: -- → S3
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(jmathies)
Priority: -- → P3

Media team feels this is site specific, and not a browser issue. It's TikTok so we should definitely reach out. FYI @Kapil has been trying to get a hold of them.

Severity: S3 → --
Component: Audio/Video: Playback → Desktop
Priority: P3 → --
Product: Core → Web Compatibility
No longer blocks: media-triage

The issue is still reproducible on the latest Nightly (111.0a1 (2023-01-31)/Windows 10). Any updates from Kapil?

Flags: needinfo?(jmathies)

I don't think we've made any good contacts with them.

Flags: needinfo?(jmathies)

Verified this issue and could not reproduce it on Firefox versions 122 and 124.

If the reporter can confirm that the issue reproduces in a new profile, we will gladly re-open the issue.

Tested with:

Browser / Version: Firefox Release 122.0. (64-bit)/ Firefox Nightly 124.0a1 (2024-01-25) (64-bit)
Operating System: Windows 10 PRO x64

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: