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 4768

Summary: direct3d renderer: SDL_DestroyTexture after SDL_RenderCopy prevents texture drawing
Product: SDL Reporter: Alexander Maltsev <keltar.gw>
Component: renderAssignee: Ryan C. Gordon <icculus>
Status: RESOLVED FIXED QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2 CC: icculus
Version: 2.0.10Keywords: target-2.0.12
Hardware: x86_64   
OS: Windows 7   
Attachments: example demonstrating a problem

Description Alexander Maltsev 2019-08-20 04:31:26 UTC 
Created attachment 3930 [details]
example demonstrating a problem

As described in https://stackoverflow.com/questions/57547699/blank-screen-after-rendering-text , calling RenderCopy of temporary texture and DestroyTexture immediately after that results in no-draw on direct3d backend. Tested with multiple versions, problem first appeared after commit https://hg.libsdl.org/SDL/rev/5b0c4bfbd083 fixing #4460 .
Comment 1 Ryan C. Gordon 2019-09-02 04:12:43 UTC 
This is fixed in https://hg.libsdl.org/SDL/rev/6ee12b88beed, thanks!

--ryan.
Comment 2 Ryan C. Gordon 2019-09-20 20:47:35 UTC 
We're changing how we do SDL release versions; now releases will be even numbers (2.0.10, 2.0.12, etc), and as soon as we tag a release, we'll move the internal version number to an odd number (2.0.12 ships, we tag the latest in revision control as 2.0.13 immediately, which will become 2.0.14 on release, etc).

As such, I'm moving the bugs tagged with target-2.0.11 to target 2.0.12. Sorry if you get a lot of email from this change!

Thanks,
--ryan.
Comment 3 Ryan C. Gordon 2019-09-20 20:48:44 UTC 
We're changing how we do SDL release versions; now releases will be even numbers (2.0.10, 2.0.12, etc), and as soon as we tag a release, we'll move the internal version number to an odd number (2.0.12 ships, we tag the latest in revision control as 2.0.13 immediately, which will become 2.0.14 on release, etc).

As such, I'm moving the bugs tagged with target-2.0.11 to target 2.0.12. Sorry if you get a lot of email from this change!

Thanks,
--ryan.