Closed
Bug 1661189
Opened 5 years ago
Closed 5 years ago
Make directly texture bounded buffers are not held by AsyncImagePipelineManager::mTexturesInUseByGPU on Android
Categories
(Core :: Graphics: WebRender, enhancement)
Core
Graphics: WebRender
Tracking
()
RESOLVED
FIXED
82 Branch
Tracking | Status | |
---|---|---|
firefox82 | --- | fixed |
People
(Reporter: sotaro, Assigned: sotaro)
References
Details
Attachments
(1 file, 1 obsolete file)
On android, mLatestRenderFrameId could be used as LastCompletedFrameId, since android fence is used to wait reusing of a directly texture bounded buffer if it is still used by gpu/hardware.
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → sotaro.ikeda.g
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Summary: Use mLatestRenderFrameId as LastCompletedFrameId at RenderCompositorEGL on Android → Make directly texture bounded buffers are not held by AsyncImagePipelineManager::mTexturesInUseByGPU on Android
Assignee | ||
Comment 2•5 years ago
|
||
Updated•5 years ago
|
Attachment #9172583 -
Attachment is obsolete: true
Updated•5 years ago
|
Attachment #9172071 -
Attachment description: Bug 1661189 - Use mLatestRenderFrameId as LastCompletedFrameId at RenderCompositorEGL on Android → Bug 1661189 - Make directly texture bounded buffers are not held by AsyncImagePipelineManager::mTexturesInUseByGPU on Android
Pushed by sikeda.birchill@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/37b3648fa315
Make directly texture bounded buffers are not held by AsyncImagePipelineManager::mTexturesInUseByGPU on Android r=mattwoodrow
Comment 4•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox82:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
Assignee | ||
Updated•5 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•