-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Going between direct scanout and compositing causes a several second freeze #310
Comments
Huh, wtf. Never seen this (and I play plenty of Lazer).
Is there perhaps any more specific condition that you've noticed when it happens? Also does it just happen for a few minutes then stops? Seems like I don't currently have a debug flag to disable direct scanout; this is what I'd test. |
Not really, it's pretty random, I've had this issue not only with osu!, but also with Cities Skylines on Gamescope, Zoom web version in Firefox and Youtube in Firefox. The only constants are that I always have firefox opened and it affects a fullscreened window. I'm currently trying to find a way to reproduce, if I find a way I'll add a comment explaining how to.
It doesn't stop until I restart niri. |
I just pushed a flag to disable direct scanout, could you rebuild niri and try if it helps next time you hit this issue?
|
Thanks, I'll rebuild and test with the new flag. |
Any news? |
I tested the new flag and haven't had the issue ever since. |
I see. It is really weird that you get a freeze on direct scanout, but I'm not sure if there's an easy way to diagnose. |
I'll close the issue because I'm not sure there's anything actionable I can do here at the moment, but feel free to reopen if some new details come up. |
Something that may help to debug this is getting a DRM debug log, if you feel like it. The process is described here: https://gitlab.freedesktop.org/wlroots/wlroots/-/wikis/DRM-Debugging Specifically, you'd need to do this:
Running niri with |
I updated to version 0.1.6 and enabled direct scanout to try and reproduce the issue, I got a DRM debug log of the issue while playing osu! lazer. I still have no idea how to reproduce other than a fullscreen app and wait to see the error. |
Thanks! cc @cmeissl who can maybe tell what's wrong from this |
I also got niri's log with |
Thanks. That does not seem particularly related. |
I will also get freeze when enter fullscreen (whether mete+shift+f or media site’s own fullscreen), then add this debug flag can “fixed” it. GPU: Nvidia - 4060 |
I found a warn message when entered the fullscreen mode. Maybe it caused?
and some
|
Sorry for late reply. The only thing that stood out from the log is that it seems to disable and re-enable the plane in the commit. The log contains multiple entries of
I have no AMD hardware at hand so that might also be expected, but it sounds suspicious. Especially the @migue07juegos Can you please also post the output of |
The warning about legacy fbadd is definitely suspicious, but imo should not cause a freeze. |
@cmeissl here is the output of drm_info. I'm currently trying to get the trace log, but I haven't had the issue yet since recompiling and activating direct scanout. If I get the error again I'll add a message with the trace log. |
Sometimes a fullscreened window causes lag when switching to another window, it freezes for about 5 seconds and then everything is back to normal, and also the other way around, when switching from another window to the fullscreened window.
The video isn't lagging, that's what I see on my monitor. I move the cursor in circles so it's easier to show how it freezes and unfreezes. Also the audio doesn't have any issues, so I guess it is only niri freezing.
compressed.mp4
System Information
niri.save2.log
The text was updated successfully, but these errors were encountered: