Closed
Bug 1031500
Opened 10 years ago
Closed 10 years ago
Expose graphic Buffer to MediaCodec
Categories
(Core :: Audio/Video, defect)
Tracking
()
People
(Reporter: jesup, Assigned: jesup)
References
Details
Attachments
(1 file)
1.38 KB,
patch
|
sotaro
:
review+
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a clone of Bug #1009410 +++ WebRTC OMX H.264 decode ends up blocked on buffers; as a near-term workaround, increase the number of buffers for WebRTC. Note that the codec can only do HVGA @30fps @700Kbps when used for encode and decode at once, so that limits the memory hit.
Assignee | ||
Comment 1•10 years ago
|
||
jhlin's patch from bug 1009410
Assignee | ||
Updated•10 years ago
|
Attachment #8447381 -
Flags: review?(sotaro.ikeda.g)
Assignee | ||
Updated•10 years ago
|
Blocks: 989945
blocking-b2g: --- → 2.0?
status-b2g-v2.0:
--- → affected
status-firefox32:
--- → affected
status-firefox33:
--- → affected
Whiteboard: [webrtc-uplift]
Comment 2•10 years ago
|
||
Comment on attachment 8447381 [details] [diff] [review] Increase number of buffers for webrtc OMX H.264 decode Review of attachment 8447381 [details] [diff] [review]: ----------------------------------------------------------------- Rview+ if the hardcoded "10" defined in another place. Hard-code a number directly to a function's argument is not good.
Attachment #8447381 -
Flags: review?(sotaro.ikeda.g) → review+
Comment 3•10 years ago
|
||
(In reply to Randell Jesup [:jesup] from comment #0) > WebRTC OMX H.264 decode ends up blocked on buffers; as a near-term > workaround, increase the number of buffers for WebRTC. Please file a bug for undoing that workaround (once this lands at the latest).
Updated•10 years ago
|
blocking-b2g: 2.0? → 2.0+
Assignee | ||
Comment 4•10 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/febfad44b731
Target Milestone: --- → mozilla33
Comment 5•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/febfad44b731
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•10 years ago
|
||
Comment on attachment 8447381 [details] [diff] [review] Increase number of buffers for webrtc OMX H.264 decode Approval Request Comment [Feature/regressing bug #]: N/A [User impact if declined]: Jerking/low-frame-rate in B2G Webrtc with HW H.264 (8x10/Flame) [Describe test coverage new/current, TBPL]: On M-c since last week [Risks and why]: Only risk is memory use; the extra buffers are only used in WebRTC H.264 OMX calls [String/UUID change made/needed]: None
Attachment #8447381 -
Flags: approval-mozilla-aurora?
Comment 7•10 years ago
|
||
Comment on attachment 8447381 [details] [diff] [review] Increase number of buffers for webrtc OMX H.264 decode 2.0+ have auto-approval for Aurora.
Attachment #8447381 -
Flags: approval-mozilla-aurora?
Comment 8•10 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/75f0e9ea8629
status-b2g-v2.1:
--- → fixed
status-firefox31:
--- → wontfix
Comment 9•10 years ago
|
||
(In reply to Florian Bender from comment #3) > (In reply to Randell Jesup [:jesup] from comment #0) > > WebRTC OMX H.264 decode ends up blocked on buffers; as a near-term > > workaround, increase the number of buffers for WebRTC. > > Please file a bug for undoing that workaround (once this lands at the > latest). It should be bug 1009410.
Assignee | ||
Updated•10 years ago
|
Whiteboard: [webrtc-uplift]
You need to log in
before you can comment on or make changes to this bug.
Description
•