зеркало из https://github.com/mozilla/gecko-dev.git
daf06d791b
Without CoreAnimation, back-pressure was applied by SwapBuffers: On a double-buffered NSOpenGLContext which is bound to an NSView, [context flushBuffer] waits for the previous frame to be finished. With CoreAnimation, the context is no longer bound to an NSView, and SwapBuffers acts as a regular glFlush. glFlush on its own does not prevent overproduction. If we submit GPU work at a faster rate than the GPU can handle, we end up delaying the window server's GPU work. This can cause the window server to skip frames. So even if Gecko can produce frames at 60FPS, the window server might only present those frames at 30FPS, skipping every second frame. Differential Revision: https://phabricator.services.mozilla.com/D26412 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| Moz2DImageRenderer.cpp | ||
| README.webrender | ||
| RenderAndroidSurfaceTextureHostOGL.cpp | ||
| RenderAndroidSurfaceTextureHostOGL.h | ||
| RenderBufferTextureHost.cpp | ||
| RenderBufferTextureHost.h | ||
| RenderCompositor.cpp | ||
| RenderCompositor.h | ||
| RenderCompositorANGLE.cpp | ||
| RenderCompositorANGLE.h | ||
| RenderCompositorEGL.cpp | ||
| RenderCompositorEGL.h | ||
| RenderCompositorOGL.cpp | ||
| RenderCompositorOGL.h | ||
| RenderD3D11TextureHostOGL.cpp | ||
| RenderD3D11TextureHostOGL.h | ||
| RenderEGLImageTextureHost.cpp | ||
| RenderEGLImageTextureHost.h | ||
| RenderMacIOSurfaceTextureHostOGL.cpp | ||
| RenderMacIOSurfaceTextureHostOGL.h | ||
| RenderSharedSurfaceTextureHost.cpp | ||
| RenderSharedSurfaceTextureHost.h | ||
| RenderTextureHost.cpp | ||
| RenderTextureHost.h | ||
| RenderTextureHostOGL.cpp | ||
| RenderTextureHostOGL.h | ||
| RenderTextureHostWrapper.cpp | ||
| RenderTextureHostWrapper.h | ||
| RenderThread.cpp | ||
| RenderThread.h | ||
| RendererOGL.cpp | ||
| RendererOGL.h | ||
| RendererScreenshotGrabber.cpp | ||
| RendererScreenshotGrabber.h | ||
| WebRenderAPI.cpp | ||
| WebRenderAPI.h | ||
| WebRenderTypes.cpp | ||
| WebRenderTypes.h | ||
| cbindgen.toml | ||
| moz.build | ||
| rustfmt.toml | ||
| webrender_ffi.h | ||
README.webrender
To build and run WebRender in Gecko:
1. Install Rust if you don't have it already
If you are doing gecko builds already, you should already have Rust as it is a build requirement.
If not, you can install it using |mach bootstrap| (recommended) or from https://www.rust-lang.org/
Note: If installing manually, use the stable 64-bit release - on Windows make sure to use the MSVC ABI installer.
Ensure that rustc and cargo are in your $PATH (adding $HOME/.cargo/bin/ should be sufficient)
2. Build using |mach build|.
You don't need anything special in your mozconfig for local builds; webrender will be built by default.
3. Run with |MOZ_WEBRENDER=1| in your environment. e.g. |MOZ_WEBRENDER=1 ./mach run|.
Alternatively, you can set the gfx.webrender.enabled pref to true (browser restart required).
Note that on Linux, acceleration is disabled by default and it needs to be enabled for WebRender to work.
On Linux you can enable acceleration by putting |MOZ_ACCELERATED=1| in your environment, or setting layers.acceleration.force-enabled to true in about:config.
4. Verify WebRender is enabled. You can do this by going to about:support and checking the "Compositing" line in the Graphics section. It should say "WebRender".
There should also be a WebRender section under "Decision Log" in about:support, which will provide some more detail on what caused it to be enabled/disabled.
When making changes:
- Make the changes you want.
- Run |mach build| or |mach build binaries| as desired.
For a debug webrender build:
Use a debug mozconfig (ac_add_options --enable-debug)
You can also use an opt build but make webrender less optimized by putting opt-level=0 in the [profile.release] section of your toolkit/library/rust/Cargo.toml file
See also https://groups.google.com/forum/#!topic/mozilla.dev.servo/MbeMcqqO1fs