You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The linked discord message also has a different video of the same problem, but posted by KETAL.
Steps to reproduce
Run an example that uses Silk windowing on Linux+Wayland+KDE and try to resize the window.
The window should behave similarly to the video above.
Comments
I didn't do much debugging since this is out of my area.
Only changes I made were to remove the Android, iOS, and similar target frameworks so I can build and run the solution.
This should be unrelated to the issue.
I did some profiling and found this happens because of the GLFW Refresh callback. That callback triggers the entire update and draw callbacks again, and forces the window to call glfwSwapBuffers. Disabling this callback fixes the problem.
I suspect this will have been added to allow the window to continue rendering on Windows when the window is resized (I have not verified the behaviour on Windows, I do not have a Windows machine with me).
How do you propose this is resolved? I propose that we just remove the callback altogether, however that may be a breaking change depending on the application.
I'm experiencing this issue as well. Until this is resolved in Silk.NET, below is an admittedly hacky workaround that works for my use-case. May be useful for anyone else coming across this.
Activity
aquagoose commentedon May 13, 2026
I did some profiling and found this happens because of the GLFW Refresh callback. That callback triggers the entire update and draw callbacks again, and forces the window to call
glfwSwapBuffers. Disabling this callback fixes the problem.I suspect this will have been added to allow the window to continue rendering on Windows when the window is resized (I have not verified the behaviour on Windows, I do not have a Windows machine with me).
How do you propose this is resolved? I propose that we just remove the callback altogether, however that may be a breaking change depending on the application.
2026-05-13.01-37-49.mp4
Exanite commentedon May 13, 2026
I'm unfamiliar with the Silk windowing code so I can't say much regarding this.
The most I can do is test this later on Windows.
Exanite commentedon May 13, 2026
However, feel free to open a PR so we can more easily test and discuss the changes there.
ChaseHuegel commentedon Aug 15, 2026
I'm experiencing this issue as well. Until this is resolved in Silk.NET, below is an admittedly hacky workaround that works for my use-case. May be useful for anyone else coming across this.