Closed
Bug 1141311
Opened 10 years ago
Closed 10 years ago
Add async mode support to GonkNativeWindow on Lollipop Gonk
Categories
(Core :: Graphics, defect)
Tracking
()
People
(Reporter: sotaro, Assigned: sotaro)
References
Details
Attachments
(1 file)
(deleted),
patch
|
pchang
:
review+
bajaj
:
approval-mozilla-b2g37+
|
Details | Diff | Splinter Review |
async mode is necessary to handle return nullprt from GonkNativeWindow::getCurrentBuffer() situation. It happen when gecko side hold more than GonkBufferQueue::mMaxAcquiredBufferCount+1 buffer.
Bug 1036539 added "Add async mode support" until KK.
In android, this should not happen. But on b2g this could happen.
If it happens, GonkBufferQueue always continue to hold one additional frame.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → sotaro.ikeda.g
Assignee | ||
Updated•10 years ago
|
Assignee | ||
Comment 1•10 years ago
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #0)
>
> In android, this should not happen. But on b2g this could happen.
> If it happens, GonkBufferQueue always continue to hold one additional frame.
When we do not extend MaxAcquiredBufferCount by the following call, it is easily happen during WebRTC.
> consumer->setMaxAcquiredBufferCount(WEBRTC_OMX_H264_MIN_DECODE_BUFFERS);
Assignee | ||
Updated•10 years ago
|
Assignee | ||
Comment 3•10 years ago
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #0)
> async mode is necessary to handle return nullprt from
> GonkNativeWindow::getCurrentBuffer() situation. It happen when gecko side
> hold more than GonkBufferQueue::mMaxAcquiredBufferCount+1 buffer.
Each time when it happens, GonkBufferQueue accumulate one more buffer in the GonkBufferQueue.
Comment 4•10 years ago
|
||
Hi Sotaro, what would be the user implication of this bug on 2.2? Would it simply consume more memory than it needs to? Just want to know about its priority level. thanks!
Flags: needinfo?(sotaro.ikeda.g)
Assignee | ||
Comment 5•10 years ago
|
||
(In reply to No-Jun Park [:njpark] from comment #4)
> Hi Sotaro, what would be the user implication of this bug on 2.2? Would it
> simply consume more memory than it needs to? Just want to know about its
> priority level. thanks!
camera preview stream add more lags. It affect to the camera preview's responsiveness. And If GonkNativeWindow accumulate too much video frame, it could block camera preview update.
Flags: needinfo?(sotaro.ikeda.g)
Assignee | ||
Comment 6•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Attachment #8575392 -
Flags: review?(pchang)
Comment 7•10 years ago
|
||
Comment on attachment 8575392 [details] [diff] [review]
patch - Add async mode support to GonkNativeWindow on Lollipop Gonk
Review of attachment 8575392 [details] [diff] [review]:
-----------------------------------------------------------------
LGTM
Attachment #8575392 -
Flags: review?(pchang) → review+
Assignee | ||
Comment 8•10 years ago
|
||
Assignee | ||
Comment 9•10 years ago
|
||
Updated•10 years ago
|
Status: NEW → ASSIGNED
blocking-b2g: 2.2? → 2.2+
Comment 10•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
status-firefox39:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla39
Assignee | ||
Updated•10 years ago
|
status-b2g-v2.2:
--- → affected
Assignee | ||
Comment 11•10 years ago
|
||
Comment on attachment 8575392 [details] [diff] [review]
patch - Add async mode support to GonkNativeWindow on Lollipop Gonk
NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.
[Approval Request Comment]
Bug caused by (feature/regressing bug #): none
User impact if declined: User could face a lag of camera preview during WebRTC.
Testing completed: locally tested.
Risk to taking this patch (and alternatives if risky): low.
String or UUID changes made by this patch: none.
Attachment #8575392 -
Flags: approval-mozilla-b2g37?
Updated•10 years ago
|
Attachment #8575392 -
Flags: approval-mozilla-b2g37? → approval-mozilla-b2g37+
Comment 12•10 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•