We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 3380

Summary: Crash during 'SDL_DestroyRenderer' with valid Renderer with SDL_RENDERER_ACCELERATED
Product: SDL Reporter: timo.scholli
Component: renderAssignee: Sam Lantinga <slouken>
Status: RESOLVED ABANDONED QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2 CC: philipp.wiesemann
Version: 2.0.4   
Hardware: x86   
OS: Windows 7   
Attachments: Code that is causing the error.
right file

Description timo.scholli 2016-07-02 18:36:56 UTC 
Call Stack:

#0 0x726437a2	vrfcore!VerifierStopMessageEx() (C:\Windows\SysWOW64\vrfcore.dll:??)
#1 0x73dd4f99	?? () (??:??)
#2 0x900	?? () (??:??)
#3 ??	?? () (??:??)
Comment 1 Philipp Wiesemann 2016-07-02 21:31:14 UTC 
Is this with the "direct3d" or the "opengl" renderer? It can be checked with SDL_GetRendererInfo().

A small example program where the crash happens would also be useful. :)
Comment 2 timo.scholli 2016-07-03 14:29:00 UTC 
Created attachment 2523 [details]
Code that is causing the error.

its compiled with mingw

with follwing flags:
-lmingw32 -lSDL2main -lSDL2 -lSDL2_image -lSDL2_ttf
Comment 3 timo.scholli 2016-07-03 14:29:59 UTC 
(In reply to timo.scholli from comment #2)
> Created attachment 2523 [details]
> Code that is causing the error.
> 
> its compiled with mingw
> 
> with follwing flags:
> -lmingw32 -lSDL2main -lSDL2 -lSDL2_image -lSDL2_ttf

its with the "direct3d" Renderer
Comment 4 timo.scholli 2016-07-03 19:17:10 UTC 
Created attachment 2524 [details]
right file

sry, firt i uploaded the wrong files, here are the right ones
Comment 5 timo.scholli 2016-07-05 21:59:33 UTC 
i found out that the bug is computer specific, when i compile on a pc with an

Intel(R) Core(TM) i7-670K CPU @ 4.00 GHz 4.00 GHz (Skylake)
Asus Z170 Pro Gaming Mainboard
NVIDIA GeForce GTX 7500 Ti

the bug only appears on that pc.
I will try reinstalling my windows and look if the bug is still appearing
Comment 6 Ryan C. Gordon 2018-08-06 21:20:22 UTC 
Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.