Closed
Bug 784019
Opened 11 years ago
Closed 11 years ago
OMX.google.h264.decoder playback aborts on Android with: 'Timed out waiting for output buffers: 0/1
Categories
(Core :: Audio/Video, defect)
Tracking
()
RESOLVED
FIXED
mozilla20
People
(Reporter: aaronmt, Assigned: eflores)
References
()
Details
(Whiteboard: [swdecoder])
Attachments
(1 file)
1.80 KB,
patch
|
cajbir
:
review+
|
Details | Diff | Splinter Review |
... I/OmxPlugin( 3884): data: 0x6901f400 size: 353280 offset: 0 length: 353280 unreadable: 0 I/OmxPlugin( 3884): data: 0x68fc9000 size: 353280 offset: 0 length: 353280 unreadable: 0 I/OmxPlugin( 3884): data: 0x6901f400 size: 353280 offset: 0 length: 353280 unreadable: 0 E/OMXCodec( 3884): [OMX.google.h264.decoder] Timed out waiting for output buffers: 0/1 http://www.quirksmode.org/html5/videos/big_buck_bunny.mp4 $ adb shell am start -a android.intent.aciton.VIEW -n org.mozilla.fennec/.App -d http://www.quirksmode.org/html5/videos/big_buck_bunny.mp4 Playback begins smoothly and continues to degrade until it abruptly stops with the above message to console. -- Samsung Galaxy Nexus (Android 4.1.1) Mozilla-Inbound 20120820060900 http://hg.mozilla.org/integration/mozilla-inbound/rev/fedc45481456
Updated•11 years ago
|
tracking-fennec: ? → 16+
Updated•11 years ago
|
Whiteboard: [swdecoder]
Updated•11 years ago
|
Assignee: nobody → chris.double
tracking-fennec: 16+ → 17+
Assignee | ||
Updated•11 years ago
|
Assignee: chris.double → eflores
Comment 1•11 years ago
|
||
> Timed out waiting for output buffers: 0/1 It seems that this timed out happen when OMXCodec's client grab too much MediaBuffer. In stagefright, AwesomePlayer concurrently own at most only one video frame. following is my related comment in the past. https://bugzilla.mozilla.org/show_bug.cgi?id=714408#c78
Assignee | ||
Comment 2•11 years ago
|
||
Thought as much. It looks like it allocates far fewer buffers on my phone than it does on B2G, though. I wonder if that means we can dial it back for B2G.
Updated•11 years ago
|
tracking-fennec: 17+ → +
Assignee | ||
Comment 3•11 years ago
|
||
Well that was straightforward.
Attachment #681199 -
Flags: review?(chris.double)
Comment 4•11 years ago
|
||
How does this affect non-media plugin playback on Android? Have you done a try server run to see if it breaks anything there?
Assignee | ||
Comment 5•11 years ago
|
||
https://tbpl.mozilla.org/?tree=Try&rev=dd4dae42072c
Updated•11 years ago
|
Attachment #681199 -
Flags: review?(chris.double) → review+
Why hasn't this landed?
Assignee | ||
Comment 7•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/53c75e6f0f66
Comment 8•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/53c75e6f0f66
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla20
You need to log in
before you can comment on or make changes to this bug.
Description
•