Hi there! Time for another mozilla graphics newsletter. In the comments section of the previous newsletter, Michael asked about the relation between WebRender and WebGL, I’ll try give a short answer here.
Both WebRender and WebGL need access to the GPU to do their work. At the moment both of them use the OpenGL API, either directly or through ANGLE which emulates OpenGL on top of D3D11. They, however, each work with their own OpenGL context. Frames produced with WebGL are sent to WebRender as texture handles. WebRender, at the API level, has a single entry point for images, video frames, canvases, in short for every grid of pixels in some flavor of RGB format, be them CPU-side buffers or already in GPU memory as is normally the case for WebGL. In order to share textures between separate OpenGL contexts we rely on platform-specific APIs such as EGLImage and DXGI.
Beyond that there isn’t any fancy interaction between WebGL and WebRender. The latter sees the former as a image producer just like 2D canvases, video decoders and plain static images.
What’s new in gfx
Wayland and hidpi improvements on Linux
- Martin Stransky made a proof of concept implementation of DMABuf textures in Gecko’s IPC mechanism. This dmabuf EGL texture backend on Wayland is similar what we have on Android/Mac. Dmabuf buffers can be shared with main/compositor process, can be bound as a render target or texture and can be located at GPU memory. The same dma buf buffer can be also used as hardware overlay when it’s attached to wl_surface/wl_subsurface as wl_buffer.
- Jan Horak fixed a bug that prevented tabs from rendering after restoring a minimized window.
- Jan Horak fixed the window parenting hierarchy with Wayland.
- Jan Horak fixed a bug with hidpi that was causing select popups to render incorrectly after scrolling.
WebGL multiview rendering
WebGL’s multiview rendering extension has been approved by the working group and it’s implementation by Jeff Gilbert will be shipping in Firefox 70.
This extension allows more efficient rendering into multiple viewports, which is most commonly use by VR/AR for rendering both eyes at the same time.
Better high dynamic range support
Jean Yves landed the first part of his HDR work (a set of 14 patches). While we can’t yet output HDR content to HDR screen, this work greatly improved the correctness of the conversion from various HDR formats to low dynamic range sRGB.
You can follow progress on the color space meta bug.
What’s new in WebRender
WebRender is a GPU based 2D rendering engine for web written in Rust, currently powering Firefox‘s rendering engine as well as the research web browser servo.
If you are curious about the state of WebRender on a particular platform, up to date information is available at http://arewewebrenderyet.com
Speaking of which, darkspirit enabled webrender on Nightly for Nvidia+Nouveau drivers linux users in Firefox Nightly.
More filters in WebRender
When We run into a primitive that isn’t supported by WebRender, we make it go through software fallback implementation which can be slow for some things. SVG filters are a good example of primitives that perform much better if implemented on the GPU in WebRender.
Connor Brewster has been working on implementing a number of SVG filters in WebRender:
- Bug 1555483 – Introduce some infrastructure for SVG filters in WebRender and implement the feBlend filter.
- Bug 1178765 – Implement backdrop-filter from the Filter Effects Module Level 2 specification.
See the SVG filters in WebRender meta bug.
Texture swizzling and allocation
WebRender previously only worked with BGRA for color textures. Unfortunately this format is optimal on some platforms but sub-optimal (or even unsupported) on others. So a conversion sometimes has to happen and this conversion if done by the driver can be very costly.
Kvark reworked the texture caching logic to support using and swizzling between different formats (for example RGBA and BGRA).
A document that landed with the implementation provides more details about the approach and context.
Kvark also improved the texture cache allocation behavior.
Kvark also landed various refactorings (1), (2), (3), (4).
Jamie fixed emoji rendering on webrender on android and continues investigating driver issues on Adreno 3xx devices.
Dan replaced bincode in our DL IPC code with a new bespoke and private serialization library (peek-poke), ending the terrible reign of the secret serde deserialize_in_place hacks and our fork of serde_derive.
Picture caching improvements
Glenn landed several improvements and fixes to the picture caching infrastructure:
- Bug 1566712 – Fix quality issueswith picture caching when transform has fractional offsets.
- Bug 1572197 – Fix world clip region for preserve-3d items with picture caching.
- Bug 1566901 – Make picture caching more robust to float issues.
- Bug 1567472 – Fix bug in preserve-3d batching code in WebRender.
Font rendering improvements
Lee landed quite a few font related patches:
- Bug 1569950 – Only partially clear WR glyph caches if it is not necessary to fully clear.
- Bug 1569174 – Disable embedded bitmaps if ClearType rendering mode is forced.
- Bug 1568841 – Force GDI parameters for GDI render mode.
- Bug 1568858 – Always stretch box shadows except for Cairo.
- Bug 1568841 – Don’t use enhanced contrast on GDI fonts.
- Bug 1553818 – Use GDI ClearType contrast for GDI font gamma.
- Bug 1565158 – Allow forcing DWrite symmetric rendering mode.
- Bug 1563133 – Limit the GlyphBuffer capacity.
- Bug 1560520 – Limit the size of WebRender’s glyph cache.
- Bug 1566449 – Don’t reverse glyphs in GlyphBuffer for RTL.
- Bug 1566528 – Clamp the amount of synthetic bold extra strikes.
- Bug 1553228 – Don’t free the result of FcPatternGetString.
Various fixes and improvements
- Gankra fixed an issue with addon popups and document splitting.
- Sotaro prevented some unnecessary composites on out-of-viewport external image updates.
- Nical fixed an integer oveflow causing the browser to freeze
- Nical improved the overlay profiler by showing more relevant numbers when the timings are noisy.
- Nical fixed corrupted rendering of progressively loaded images.
- Nical added a fast path when none of the primitives of an image batch need anti-aliasing or repetition.
11 thoughts on “moz://gfx newsletter #47”
Somebody should remove https://searchfox.org/mozilla-central/rev/428cf94f4ddfb80eebc6028023a7d89eb277791b/.cargo/config.in#10-13 too, glad to see the serde-derive fork dropped!
Hi, Nical! Thanks for the explanation, it’s now clear where is WebGL placed in Firefox+WebRender HLA.
Tossing WebGL-produced textures around threads/processes is expensive, and make my CPU sad (and hot) due to 4K screen (WebRender is ON, of course), but it is known issue https://bugzilla.mozilla.org/show_bug.cgi?id=1010527, and there is a hope https://bugzilla.mozilla.org/show_bug.cgi?id=1572697.
As for your always interesting newsletters, I would humbly ask to describe one more puzzle. How WebRender works with OS compositor: direct rendering to GPU, syncing frames, and maybe even works with VRR aka FreeSync?
What’s expensive in the case of linux isn’t really sharing, it’s that we are falling back to copying the GPU memory of the WebGL texture into CPU shared memory and copying that back into GPU memory on the compositor process, and these copies can be awfully slow. On Windows for example, DXGI gives us a way to share that GPU memory directly accross contexts and processes. My hope is that dmabuf will be the way forward on Linux.
The OS compositor question is tricky because there’s what we do now and what we will do in the (hopefully near-ish) future. I’ll write about that in the next newsletter.
It looks like kernel 5.3 is going to be part of Ubuntu 19.10. Is that going to make it possible to address this issue? Right now browsing websites on my 4k screen turns the CPU into a hothead. Every time a page loads the fan spins up. I hope Linux devs out there will give your team all the tools needed to fully utilize our hardware. :)
Is there any more info on when Webrender would be enabled on Win 7?
Does DMABuf work with the proprietary Nvidia driver / EGLStreams?
Is running Webrender and WebGL through Vulkan instead of OpenGL also a possibility for the future?
Yes. It is currently not at the top of the priority list but we already have a prototype of that actually. It’ll happen in a while though.
Hey Nical. Can you please leave new blogposts more often? Every day I visit this blog in hope that there new post about amazing new features in webrender. And know what? I don’t understand all these complex words like bitmap or vertex, lol, but I just like to understand that my lovely firefox becomes stronger and faster, and can resist chrome with its tons of telemetry… Thanks for the work.
Blog idea: could you give an update to metrics of WebRender and other future looking statements from the time? https://mozillagfx.wordpress.com/2019/05/21/graphics-team-ships-webrender-mvp/
is this the last update we are in october and no news