Open
Bug 1067754
Opened 10 years ago
Updated 2 years ago
Introduce type-safety around various media clocks
Categories
(Core :: Audio/Video: Playback, defect)
Core
Audio/Video: Playback
Tracking
()
NEW
People
(Reporter: kinetik, Unassigned)
Details
Spinning this off from bug 1065715 since it's sufficiently different to be worthy of its own bug:
We've had a number of bugs in the past, either in release or during development, that would be avoidable with some type safety introduced to the various media clocks.
These issues arise from inadvertent mixing timeline calculations between start-time based and zero-based timelines. At present, the clocks are represented as a set of bare int64_ts (a start time, a current time, perhaps an end time), and because the naming and types of these bare integers can be similar and confusion, it's easy to introduce bugs into the various media clock calculations.
Updated•9 years ago
|
Component: Audio/Video → Audio/Video: MSG/cubeb/GMP
Updated•9 years ago
|
Component: Audio/Video: MediaStreamGraph → Audio/Video: Playback
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•