Open Bug 1893885 Opened 9 months ago Updated 2 months ago

Reduced time precision in media currentTime

Categories

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

Firefox 126
defect

Tracking

()

Tracking Status
firefox126 --- affected
firefox127 --- affected
firefox128 --- affected

People

(Reporter: ble-m, Unassigned)

Details

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

Steps to reproduce:

  1. Visit https://gh.ltgc.cc/octavia/test/fakeQy.htm (as an example).
  2. Execute self.debugTimeSource = true; in the console to get the player emit timestamps.
  3. Play any of the listed demos, and see the time value emitting in the console.

Actual results:

Value of the currentTime property gets increased in a 40 millisecond step with random jitters, instead of the 2-millisecond precision when privacy.reduceTimerPrecision is enabled. This weird stepping doesn't go away when privacy.reduceTimerPrecision is disabled.

Expected results:

Value of currentTime should've been increased smoothly, like on Chromium browsers.

The bug was spotted on 126.0b6 (Dev Edition), and confirmed to exist from 115.10.0 (ESR), all the way to 127.0b1 (Nightly Build available at the time of the report).

Managed to reproduce this issue on:

  • Firefox Nightly 128.0a1;
  • Firefox Beta 127.0b1;
  • Firefox 126.0;

Tested and reproduced on:

  • Windows 10;
  • macOS 12;
  • Ubuntu 22;

Setting to Product to ‘DevTools’ and the Component to ‘Console’ . Please change if there’s a better fit, thank you.
Setting as NEW so the developing team can have a look.

Status: UNCONFIRMED → NEW
Component: Untriaged → Console
Ever confirmed: true
Product: Firefox → DevTools

Console is only used to diagnose the issue. Moving to more appropriate module so the right folks can have a look

Component: Console → Audio/Video: Playback
Product: DevTools → Core

Does this reproduce in Chrome?

Flags: needinfo?(ble-m)

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

Does this reproduce in Chrome?

No, at least not in the abysmal time interval Firefox currently has.

Flags: needinfo?(ble-m)
Severity: -- → S3
You need to log in before you can comment on or make changes to this bug.