Closed Bug 947038 Opened 11 years ago Closed 10 years ago

Switch the basic compositor to use new textures

Categories

(Core :: Graphics: Layers, defect)

All
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 989904

People

(Reporter: dvander, Assigned: evilpie)

References

Details

Attachments

(2 files)

The software compositor still uses deprecated textures, it should be okay to force new textures for LAYERS_BASIC everywhere.
Comment on attachment 8344132 [details] [diff] [review]
ensure-deprecated-textures.patch

Review of attachment 8344132 [details] [diff] [review]:
-----------------------------------------------------------------

::: gfx/layers/ipc/CompositorParent.cpp
@@ +596,5 @@
>  
>    mCompositionManager->ComputeRotation();
>  
>  #ifdef MOZ_DUMP_PAINTING
> +  static bool gDumpCompositorTree = true;

Don't land this!
Attachment #8344132 - Flags: review?(matt.woodrow) → review+
Comment on attachment 8344132 [details] [diff] [review]
ensure-deprecated-textures.patch

Review of attachment 8344132 [details] [diff] [review]:
-----------------------------------------------------------------

David, what's the intent behind this change? Perhaps comments in the code or in the bug would help, but I can't tell why SetCompositorBackend() belongs in gfxPlatform and why it's "set only once", why the strange code in ContentClient.cpp, what of this is temporary, what is meant to stay, etc.
Attachment #8344132 - Flags: feedback-
The intent is to remove dependencies on deprecated paths in the software compositor. I'm not sure why that's strange. Most of the code here is contained in areas that will clearly go away when deprecated textures are finally removed.

https://hg.mozilla.org/integration/mozilla-inbound/rev/b6f9dbc91dc4
Thanks for the links. It's not immediately clear to me how GetBuffer() could return something invalid after Allocate() succeeds. Will debug tomorrow.
(In reply to David Anderson [:dvander] from comment #4)
> The intent is to remove dependencies on deprecated paths in the software
> compositor. I'm not sure why that's strange. Most of the code here is
> contained in areas that will clearly go away when deprecated textures are
> finally removed.
> 
> https://hg.mozilla.org/integration/mozilla-inbound/rev/b6f9dbc91dc4

Having a function with "deprecated textures" in it marks it pretty clearly for removal when the deprecated textures are gone.  Having an API to set the compositor backend layer type on gfxPlatform, and only do it once (so that the second call to that function is a no-op, assert non-withstanding) isn't really obviously in need of a removal when deprecated textures go away.
Nical, where is this bug in this picture: Nical, where is this bug in this picture: https://wiki.mozilla.org/Platform/GFX/textures#Planned_work ?
Flags: needinfo?(nical.bugzilla)
(In reply to Milan Sreckovic [:milan] from comment #8)
> Nical, where is this bug in this picture: Nical, where is this bug in this
> picture: https://wiki.mozilla.org/Platform/GFX/textures#Planned_work ?

That needs to be added to the diagram. What platforms uses basic OMTC these days?
Flags: needinfo?(nical.bugzilla)
(In reply to Nicolas Silva [:nical] from comment #9)
> (In reply to Milan Sreckovic [:milan] from comment #8)
> > Nical, where is this bug in this picture: Nical, where is this bug in this
> > picture: https://wiki.mozilla.org/Platform/GFX/textures#Planned_work ?
> 
> That needs to be added to the diagram. What platforms uses basic OMTC these
> days?

e10s
Assignee: dvander → evilpies
Attachment #8370599 - Flags: review?(nical.bugzilla)
Attachment #8370599 - Flags: review?(nical.bugzilla) → review+
Looks like on Windows, when you driver is blocked, we actually use the basic compositor even without the pref.
Blocks: NewTextures
Seems like this was done in bug 989904. Ping here if something else needs to be done.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: