-
Notifications
You must be signed in to change notification settings - Fork 2k
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
testpopup segfaults with direct3d11 renderer #10494
Comments
When building with MSVC's address sanitizer, I get an immediate
|
slouken
added a commit
to slouken/SDL
that referenced
this issue
Aug 7, 2024
slouken
added a commit
to slouken/SDL
that referenced
this issue
Aug 7, 2024
If there are bugs it's possible that the window pointer is invalid. Double check it before sending the application events and potentially dereferencing it. This showed up in libsdl-org#10494 as a window getting mouse focus as it was being destroyed and then crashing later when mouse focus was set to a different window.
slouken
added a commit
that referenced
this issue
Aug 7, 2024
slouken
added a commit
that referenced
this issue
Aug 7, 2024
If there are bugs it's possible that the window pointer is invalid. Double check it before sending the application events and potentially dereferencing it. This showed up in #10494 as a window getting mouse focus as it was being destroyed and then crashing later when mouse focus was set to a different window.
Fixed, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When randomly clicking with the left and right mouse in the testpop example, a segfault occurs.
When running under sdlprocdump, I see a few
bad_alloc
andcom_error
exceptions before segfaulting..Call stack
Inside this call:
SDL/src/render/direct3d11/SDL_render_d3d11.c
Lines 2415 to 2421 in fe5dcf7
rendererData->vertexShaderConstants
, the first argument ofID3D11DeviceContext::UpdateSubresource
is NULL.The text was updated successfully, but these errors were encountered: