Closed Bug 1654169 Opened 4 years ago Closed 4 years ago

Sync surface of GeckoSurface always uses non single buffer surface

Categories

(Core :: Graphics, enhancement)

enhancement

Tracking

()

RESOLVED FIXED
81 Branch
Tracking Status
firefox81 --- fixed

People

(Reporter: sotaro, Assigned: sotaro)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

SyncSurface of GeckoSurface always uses non single buffer surface. non single buffer surface uses more memory than singe buffer surface.

https://searchfox.org/mozilla-central/rev/9b282b34b5aa0f836beb735656c55efb2cc4c617/mobile/android/geckoview/src/main/java/org/mozilla/gecko/gfx/GeckoSurface.java#119

Assignee: nobody → sotaro.ikeda.g
Blocks: 1639280
Summary: SyncSurface of GeckoSurface always uses non single buffer surface → Sync surface of GeckoSurface always uses non single buffer surface

:jhlin, is there a reason why single buffer mode surface is not used for sync surface?

Flags: needinfo?(jolin)

(In reply to Sotaro Ikeda [:sotaro] from comment #2)

:jhlin, is there a reason why single buffer mode surface is not used for sync surface?

Not really. Thanks for the help!

Flags: needinfo?(jolin)

Sync surface is used only when content process uses GonkSurfaceTexture. The following diagram might help to understand it.

Pushed by sikeda.birchill@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/faa4b21ccbf2
Use single buffered mode surface as sync surfacce if possible r=geckoview-reviewers,snorp
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 81 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: