1469264 - Browser extremely slow with color management always enabled

Status: VERIFIED FIXED

(Core :: Graphics: Color Management, defect)

Description

[Emanuel Hoogeveen [:ehoogeveen]]

Since the 2018-06-16 Nightly, Firefox has felt extremely sluggish for me. Every input takes half a second to register, and with Webrender enabled painting feels like it's happening at ~3fps. I tracked this down to a small change from bug 1464039: https://hg.mozilla.org/integration/mozilla-inbound/rev/dfcc5301e872

My monitor is calibrated and profiled using an X-Rite ColorMunki Display and the open source ArgyllCMS toolkit. I'm using a LUT profile which requires gfx.color_management.enablev4 == true, and I'm applying it to every image using gfx.color_management.mode == 1.

If I set gfx.color_management.mode to 2 (the default), the performance issue goes away. So it seems something in my profile is triggering this path, and it makes everything extremely slow. I'm uploading my profile so you can have a look.

I'm on Windows 10 x64 revision 1803 (the April 2018 update), using the 64-bit Nightly, and my graphics card is a GeForce GTX 1080 with the latest drivers. I see the same problem on my laptop with a GeForce GTX 1060 and a different profile (but generated in the same way).

I'm not sure what the policy is on bugs that (should) block security bugs so I've marked this as security sensitive for now.

Steps to reproduce:
Starting from a fresh profile,
1) Set gfx.color_management.display_profile to the location of the profile (or set the profile as your monitor profile system-wide)
2) Set gfx.color_management.enablev4 to true
3) Set gfx.color_management.mode to 1
4) Set gfx.webrender.all to true (optional)
5) Restart the browser

Expected result:
Firefox performs as normal.

Actual result:
Firefox takes a long time to respond to inputs. With Webrender enabled, the framerate on animations is very low.

Comment 1

[Emanuel Hoogeveen [:ehoogeveen]]

Attachment: Profile for desktop monitor

Comment 3

[Ryan VanderMeulen [:RyanVM]]

Affects users with a non-default pref set, so I don't believe this needs tracking. That said, this doesn't sound great either.

Comment 4

[Emanuel Hoogeveen [:ehoogeveen]]

Sorry about the dupe, things went a bit wrong when I submitted.

Comment 5

[Nicolas Silva [:nical]]

I addressed this in the regressing bug, This should be fixed now.

Comment 6

[Emanuel Hoogeveen [:ehoogeveen]]

Yes, performance is back to normal in the latest Nightly. Thanks!