-
Notifications
You must be signed in to change notification settings - Fork 50
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
application freeze on niceDCV resize desktop operation #133
Comments
I ran a minimal sample project on the target machine building the GLwpfControl on my own in debug, when running and resizing the desktop I get the following stack trace:
The code looks like this (just played with various settings for Profile, ContextFlag and versions but they don't change a thing): public partial class MainWindow : Window
} |
And another update... Sorry for all the noise. But maybe it helps the desperate soul. On the server side of Nice DCV the option "IDD Driver" needs to be disabled. |
This feels like we want to investigate why it is happening and if there is some way for us to support this. I'm guessing the crash is because the IDD driver does some resize operation while our code doesn't expect it.. |
Hi, happy to help and test this. The resizing works fine without IDD. I closed this since it felt like a very rare use case. |
It might be a very rare use case, but it would be good to know why it happens and if any other software causes the same issue. (oops I managed to close the issue, reopened again) |
I am having an interesting issue to report. I am using OpenTK within a windows WPF application. It works perfectly fine and I am doing very basic OpenGL stuff in there (mainly visualizing a videostream).
I encountered an issue when using my application on an AWS instance using niceDCV. niceDCV has a feature where you can resize the windows and it does resize the "remote" desktop accordingly (that behaviour can be switched off however).
My application starts to freeze whenever this kind of operation takes place. I managed to create a stack trace and it mostly looks like this:
System.Threading.WaitHandle.WaitOneNoCheck(Int32)
System.Windows.Interop.D3DImage.LockImpl(System.Windows.Duration)
System.Windows.Interop.D3DImage.Lock()
OpenTK.Wpf.GLWpfControlRenderer.Render(System.Windows.Media.DrawingContext)
OpenTK.Wpf.GLWpfControl.OnRender(System.Windows.Media.DrawingContext)
System.Windows.UIElement.Arrange(System.Windows.Rect)
System.Windows.ContextLayoutManager.UpdateLayout()
System.Windows.ContextLayoutManager.UpdateLayoutCallback(System.Object)
[...]
I am a little bit lost on how to further debug or fix this issue. It "feels" like some d3d handle got disposed without OpenTK's knowledge. Any input/hint appreciated !
The text was updated successfully, but these errors were encountered: