XRes seems to (inaccurately) report memory usage for X pixmaps: https://searchfox.org/mozilla-central/rev/5a1a34953a26117f3be1a00db20c8bbdc03273d6/testing/talos/talos/cmanager_linux.py#124-141 https://www.freedesktop.org/wiki/Software/xrestop/ According to this, linux64 is running on Ubuntu 16.04: https://searchfox.org/mozilla-central/rev/5a1a34953a26117f3be1a00db20c8bbdc03273d6/taskcluster/ci/test/test-platforms.yml#120 The [try build](https://treeherder.mozilla.org/jobs?repo=try&revision=ed39b214afb83f76bcb45739bcedb81a86155644) had two WebGL test failures, which made me think of bug 1663152. According to https://wiki.mozilla.org/TestEngineering/Performance/Platforms#HPE_Moonshot it's running on an Intel APU though, but is that information correct? Do you see the same problem when running talos on [linux1804-64-shippable-qr](https://searchfox.org/mozilla-central/rev/5a1a34953a26117f3be1a00db20c8bbdc03273d6/taskcluster/ci/test/test-platforms.yml#90)? Which prefs are actually enabled? We might not be comparing GLX with EGL, but with EGL+DMABUF: Do you get the same result with widget.dmabuf-webgl.enabled=false? rasterflood_gradient sets layout.frame_rate to 0: https://searchfox.org/mozilla-central/rev/5a1a34953a26117f3be1a00db20c8bbdc03273d6/testing/talos/talos/test.py#1149 tp5o_webext also uses XRes: https://searchfox.org/mozilla-central/rev/5a1a34953a26117f3be1a00db20c8bbdc03273d6/testing/talos/talos/unittests/test_config.py#719 Since bug 1650583 comment 30, EGL no longer uses GLX_SGI_video_sync (IIUC vsync/framerate detection) because mixing them would break EGL on proprietary Nvidia. Bug 1669275 should reintroduce that only for Mesa, not for proprietary Nvidia. (bug 1640779 is about EGL-only vsync.) Since bug 1663003 comment 17, GLX is used again to find X Visual for EGL window transparency. Are there leaks or something like that?
Bug 1675768 Comment 13 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
XRes seems to (inaccurately) report memory usage for X pixmaps: https://searchfox.org/mozilla-central/rev/5a1a34953a26117f3be1a00db20c8bbdc03273d6/testing/talos/talos/cmanager_linux.py#124-141 https://www.freedesktop.org/wiki/Software/xrestop/ According to this, linux64 is running on Ubuntu 16.04: https://searchfox.org/mozilla-central/rev/5a1a34953a26117f3be1a00db20c8bbdc03273d6/taskcluster/ci/test/test-platforms.yml#120 The [try build](https://treeherder.mozilla.org/jobs?repo=try&revision=ed39b214afb83f76bcb45739bcedb81a86155644) had two WebGL test failures, which made me think of bug 1663152. According to https://wiki.mozilla.org/TestEngineering/Performance/Platforms#HPE_Moonshot it's running on an Intel APU though, but is that information correct? Do you see the same problem when running talos on [linux1804-64-shippable-qr](https://searchfox.org/mozilla-central/rev/5a1a34953a26117f3be1a00db20c8bbdc03273d6/taskcluster/ci/test/test-platforms.yml#90)? Which prefs are actually enabled? We might not be comparing GLX with EGL, but with EGL+DMABUF: Do you get the same result with widget.dmabuf-webgl.enabled=false? (Only Mesa supports DMABUF. Proprietary Nvidia falls back to readback.) rasterflood_gradient sets layout.frame_rate to 0: https://searchfox.org/mozilla-central/rev/5a1a34953a26117f3be1a00db20c8bbdc03273d6/testing/talos/talos/test.py#1149 tp5o_webext also uses XRes: https://searchfox.org/mozilla-central/rev/5a1a34953a26117f3be1a00db20c8bbdc03273d6/testing/talos/talos/unittests/test_config.py#719 Since bug 1650583 comment 30, EGL no longer uses GLX_SGI_video_sync (IIUC vsync/framerate detection) because mixing them would break EGL on proprietary Nvidia. Bug 1669275 should reintroduce that only for Mesa, not for proprietary Nvidia. (bug 1640779 is about EGL-only vsync.) Since bug 1663003 comment 17, GLX is used again to find X Visual for EGL window transparency. Are there leaks or something like that?