WebRender newsletter #39

Hi there! The project keeps making very good progress (only 7 blocker bugs left at the time of writing these words, some of which have fixes in review). This mean WebRender has a good chance of making it in Firefox 67 stable. I expect bugs and crash reports to spike as WebRender reaches a larger user population, which will keep us busy for a short while, and once things settle we’ll be able to go back to something we have been postponing for a while: polishing, adding new features and preparing WebRender for new platforms. Exciting!
I’d like to showcase a few projects that use WebRender in a future WebRender newsletter. If you maintain or know about one, please let us know in the comments section of this post.

Notable WebRender and Gecko changes

  • Jeff experimented with enabling WebRender for a few more configurations.
  • Kats enabled more WPT tests for windows-qr
  • Kvark fixed more perspective interpolation issues.
  • Kvark improved the way the resolution of transformed intermediate surfaces is computed and followed up with more improvements.
  • Kvark fixed some plane-splitting bugs.
  • Kvark prevented a crash with non-mappable clip rects.
  • Andrew fixed a pixel snapping issue.
  • srijs and Lee worked around yet another Mac GLSL compiler bug.
  • Lee fixed a performance regression related to animated blobs being invalidated too frequently.
  • Emilio fixed a clipping regression.
  • Glenn fixed a regression with tiled clip masks.
  • Glenn improved the performance of large blur radii by down-scaling more aggressively.
  • Glenn added more debugging infrastructure in wrench.
  • Sotaro enabled mochitest-chrome in WebRender.
  • Sotaro fixed an intermittent assertion.
  • Sotaro fixed a race condition between GPU process crashes and video playback.
  • Doug improved document splitting generalization and integration with APZ.

Blocker bugs countdown

The team keeps going through the remaining blockers (0 P2 bugs and 7 P3 bugs at the time of writing).

Enabling WebRender in Firefox Nightly

In about:config, set the pref “gfx.webrender.all” to true and restart the browser.

Reporting bugs

The best place to report bugs related to WebRender in Firefox is the Graphics :: WebRender component in bugzilla.
Note that it is possible to log in with a github account.

19 thoughts on “WebRender newsletter #39

      1. It works with Intel GPU! But in beta channel WR does not updates? Am I right?

        BTW Are there some performance numbers available?

      2. On my i3-6006/12Gb/SSD notebook FF66 Beta Webrender feels slower. I often see throbber, changing tabs. If I may help with some logs let me know.

        PS Is the webrender updated on beta channel?

  1. I’d be interested in the state of video acceleration in webrender. Does it already work on Windows/MacOS? And are there any plans to start supporting it on Linux? AFAIK webrender (or the old gpu accelerated code path) is a perquisite for accelerated video on linux.

    1. To elaborate on this: is accelerated video, lets say VAAPI, just another blob for webrender or would it require a deeper integration with the render code?

      1. Video frames can be passed to WebRender either as CPU-side buffers or GPU-side texture handles. WebRender doesn’t handle video explicitly: it just receives streams of images. I think that it should already be set up to be able to handle the cases you are interested in.
        I don’t know exactly what flavors of hardware video decoding Firefox supports on each platform. I’ll see if someone from the media playback team can chime in.

  2. HI Nical
    I use Firefox Nightly on my Windows 10 October 2018 laptop with webrender enabled… And I use Firefox Nightly on my Android. If you it is not a secret and are willing to answer the question ether way thank you. Is there any Nightly Android version that… you know of that you can enable… Webrender like you can on desktop?

    1. WebRender doesn’t work on android yet, so you can’t enable it at this time. There are a few mobile specific-features that need to be implemented before we get there.

  3. In the last post I ment Firefox reference browser not Frefox reference browser.
    There are different browsers for android,Firefox focus,Firefox reference browser, Firefox Nightly, and others.There are different browsers for android,Firefox focus,Frefox reference browser, Firefox Nightly, and others.

    1. Indeed, there are several android browsers using Gecko. WebRender isn’t usable on any of them yet as there are platform-specific pieces that need some work (the details of how we access the GPU and render into the screen aren’t exactly the same on all platforms for example), and some mobile-specific features that WebRender doesn’t support properly yet, for example the way Gecko handles zooming is different on mobile and on desktop.

      At the moment the people who occasionally work on WebRender for android have to change the build options of the reference browser and make their own builds.

      Android is an important platform for mozilla so there is no doubt that our priorities will shift towards it once WR is shipped and stable on desktop. It is too early to tell which gecko based android browsers and hardware configuration will come first.

Leave a Reply to Nical Cancel reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s