Xrandr slowdown solved with --current

I found a workaround for this issue:

I couldn’t respond again because I’m a “new user” and can’t reply more than 3 times. Continuing the discussion:

I cloned xrandr and launched a debug session. The delay (for me) is occuring during the call to XRRGetScreenResources().

This led me to discover this issue:

I think a workaround could be to call xrandr with the --current switch, which uses the current screen configuration and avoids polling for hardware. I’m not sure if this covers all use-cases though, particularly if you’re trying to detect hardware changes.

2 Likes