Closed
Bug 1191712
Opened 9 years ago
Closed 9 years ago
Use lower memory threshold for audio only source buffer
Categories
(Core :: Audio/Video: Playback, defect, P2)
Core
Audio/Video: Playback
Tracking
()
RESOLVED
DUPLICATE
of bug 1216460
Tracking | Status | |
---|---|---|
firefox42 | --- | affected |
People
(Reporter: jya, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [MemShrink:P2])
MediaSource currently uses a memory threshold of 100MiB for its sourcebuffers regardless of the content type.
While 100MiB is appropriate for video, for audio only sourcebuffer it doesn't make any sense.
100MiB of buffer to keep audio allows for over one hour of buffer.
This defeat the purpose of mediasource which allows to narrowly control what and how much data is fed to the media element.
Chrome according to their literature uses 150MB for video and 12MB for audio.
I think we could easily reduce it to 15MB which gives us over 9 minutes of audio buffer if we use YouTube as a reference.
Updated•9 years ago
|
Whiteboard: [MemShrink]
Updated•9 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P2]
Comment 1•9 years ago
|
||
Target for 43; no need to upload to 42.
Doing this in time would make more since than size. The spec does specify sizes though, and we'd need to work with player authors to make sure they work with the buffering we provide.
Priority: -- → P2
Reporter | ||
Comment 2•9 years ago
|
||
ended up being fixed in bug 1216460
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•