-
Notifications
You must be signed in to change notification settings - Fork 342
Large gamma size reported for headless outputs #2349
Comments
I am the reporting user - I am almost certain this is related to headless outputs (see the gitlab issue). I will re-test soon when I have a chance to restart sway (can't yet destroy them after creation - swaywm/sway#5522). |
Confirmed - I restarted sway and subsequently redshift/gammastep work as expected. I then created a single headless output and the issue returned. With a single headless output, the issue appears less often - but with each additional headless output, memory usage seems to increase substantially and the issue appears more often. |
Headless outputs don't support gamma. It's supposed to hit this path: wlroots/types/wlr_gamma_control_v1.c Line 182 in c72efcd
|
I think I'm experiencing a similar issue. I'm not using a headless display, but it's reporting a gamma size of |
Assuming you're running the DRM backend, can you run |
I got that value by poking around
|
Hmm, it seems like this goes through the legacy path, because the driver doesn't expose GAMMA_LUT_SIZE. Unfortunately drm_info doesn't print the legacy field, can you try again with ascent12/drm_info#59? |
|
I recompiled with debugging, and I can confirm it's getting only one output, now with |
OK. Your driver reports a zero gamma size (ie. gamma not supported), which is the same case as the headless output. Something in wlroots misbehaves with a zero gamma size. |
Like #1135, but now the gamma ramp is too big to fit on any reasonably sized tmpfs.
I have a user reporting that wlroots is returning a gamma ramp size of >billion (according to their trace): https://gitlab.com/chinstrap/gammastep/-/issues/3
Perhaps wlroots could automatically do a translation for outputs that have absurdly large gamma ramp sizes?
wlroots has migrated to gitlab.freedesktop.org. This issue has been moved to:
https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/2349
The text was updated successfully, but these errors were encountered: