-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
Infinte Recursion on the position-changed
window signal
#769
Comments
Thanks @kassick, Tell me - how did you notice this? did this cause any visual discrepancy or bug (which caused you get look at the logs?). So, this method has been to work around a long-standing issue where the shown window clone's position isn't synced with the actual window. I usually check with new gnome versions if it's still needed (realised I haven't checked in 45). This just involves commenting out that code block (that adds a For some reason a tiled window's position wasn't synced but it continually didn't move/correct it's frame (hence the recursion). |
Are you also able to comment out that code block (that adds the |
The session froze. After I rebooted, I've checked the logs |
I'll try that! |
Hopefully it's no longer needed. Otherwise, we'll need to put a guard on there to circuit break any recursive calling of the method. |
Update - looks like it's still needed (got an instance of a un-synced clone/window position). I've created a branch with a recursive guard on this method: #770. |
Describe the bug
The
position-changed
triggers anotherposition-changed
signal. If for some unknown reason the target window resists the computed x,y coordinates, the function causes an infinite recursion.To Reproduce
I don't know what triggered this situation -- I was in slack (the desktop app) and had just clicked a thread to open it in the side view, not as a new window. Maybe some popover hint implemented as a window or something totally unrelated to slack.
System information:
Please execute
./gather-system-info.sh
in you PaperWM clone and paste the output below.Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: