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 1621

Summary: SDL_CreateWindow throwing "Invalid handle was specified" exception
Product: SDL Reporter: Steven Logan <ste.log2>
Component: videoAssignee: Sam Lantinga <slouken>
Status: RESOLVED ABANDONED QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2 Keywords: target-2.0.0
Version: HG 2.0   
Hardware: x86   
OS: Other   

Description Steven Logan 2012-10-12 11:56:57 UTC 
hWnd = SDL_CreateWindow( _title.c_str(  ), SDL_WINDOWPOS_CENTERED, SDL_WINDOWPOS_CENTERED, width, height, SDL_WINDOW_OPENGL | SDL_WINDOW_SHOWN | SDL_WINDOW_RESIZABLE );

This call causes an "Invalid handle was specified" exception to be throwing before the SDL window is created. If I continually skip the exception eventually the window does appear.

The problem itself is somewhat intermittent, it can be fine for a couple of days then suddenly the exception gets thrown continuously at run time for a varied period of time.

The problem also arises in code which I have had for over a year and when the exception is thrown in one piece of code, all of them will throw it, when one of them doesn't throw it, none of them will.

I don't know how to explain this much more but if anything needs clarified let me know.

I'm using Windows 8, VS2012 Premium and also VS2010 Ultimate. I do not believe it is specific to any one of these as this problem has recently only arisen after a few months of using Windows 8.

The next step for me currently, is to completely reinstall Windows 8 and go from there.
Comment 1 Ryan C. Gordon 2013-07-12 22:16:07 UTC 
(Sorry if you get a lot of copies of this email, we're touching dozens of bug reports right now.)

Tagging a bunch of bugs as target-2.0.0, Priority 2.

This means we're in the final stretch for an official SDL 2.0.0 release! These are the bugs we really want to fix before shipping if humanly possible.

That being said, we don't promise to fix them because of this tag, we just want to make sure we don't forget to deal with them before we bless a final 2.0.0 release, and generally be organized about what we're aiming to ship.

Hopefully you'll hear more about this bug soon. If you have more information (including "this got fixed at some point, nevermind"), we would love to have you come add more information to the bug report when you have a moment.

Thanks!
--ryan.
Comment 2 Sam Lantinga 2013-07-21 15:56:53 UTC 
Can you build a debug version of SDL and turn on break on Win32 exceptions and see where this is happening in the SDL code?

Thanks!
Comment 3 Ryan C. Gordon 2018-08-06 21:20:20 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.