-
Notifications
You must be signed in to change notification settings - Fork 130
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
AttachToActiveGLContext Crashed in Windows #489
Comments
The context must be active in the thread when you call |
Thanks for you reply. |
Where exactly does the crash happen? |
What is the call stack? |
Did you initialize OpenGL context before calling |
If you don't have active GL context that you initialized, you should not be calling |
CreateDeviceAndSwapChainGL need the window handle parameter. |
Yes, you need Window handle to create the OpenGL context on Windows.
If there is no active context, you should not be calling this function. Please take a look at the example I sent. |
ok, thanks for your replay. |
https://registry.khronos.org/EGL/sdk/docs/man/html/eglGetCurrentContext.xhtml If you did not initialize a context, there is definitely no context. |
thanks for your reply |
Is there any way in Diligent Core or Diligent Engine to get the current context? |
I don't completely understand the question. |
thanks |
Is this related to |
Can you build a reproducer based on one of the Tutorials? |
After extensive testing, we found the GPU that causes the crash: [AMD Radeon HD 8670M]. |
What was the issue with this GPU? |
When using AttachToActiveGLContext on this GPU, it crashes immediately. |
I have created an OpenGL context in the main window through other methods. When I use AttachToActiveGLContext to bind the current default context, my demo crashes directly, outputting: User-defined allocator is not provided. Using default allocator. Then there is no other output and it crashes directly.
I guess the created OpenGL context is being used by another thread, and then the crash occurs when the context is bound using AttachToActiveGLContext?
The text was updated successfully, but these errors were encountered: