Comment # 82
on bug 110659
from tempel.julian@gmail.com
(In reply to Andrew Eikum from comment #81) > I've submitted a patch to Wine to throttle our calls to XResetScreenSaver to > once every five seconds: https://source.winehq.org/patches/data/169958 > > However, I'd argue our previous behavior isn't obviously wrong. What we were > doing was calling XResetScreenSaver each time we received user input on a > joystick in order to delay the screensaver coming up despite no > keyboard/mouse input. It's not obvious that this behavior was incorrect. Are > you sure you shouldn't be able to handle this behavior from a client? Thank you. Subjectively, I'd say it completely solves the issue. I don't see any noteworthy spikes in frametime graphs and I haven't noticed any suspicious stutter/blocking until now (will do some more tests to be sure). I'd be very happy if this could be included in 4.17 to increase chances that it gets picked up by one of the next Proton releases. It'd be interesting to know at what calling rate the display driver starts to have issues.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
