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 4485

Summary: SDL_PollEvent hangs for exactly 1 minute each iteration
Product: SDL Reporter: jannesdrijkoningen
Component: eventsAssignee: Sam Lantinga <slouken>
Status: RESOLVED FIXED QA Contact: Sam Lantinga <slouken>
Severity: blocker    
Priority: P2 CC: metalcaedes, noetimx
Version: 2.0.9Keywords: target-2.0.12
Hardware: x86_64   
OS: Windows 10   
Attachments: Bare Project

Description jannesdrijkoningen 2019-02-02 00:27:29 UTC 
I recently migrated an SDL project from 32bit to 64bit to take advantage of the extra system resources which are available in 64bit. Unfortunately this did not go as smooth as I expected it to be. For some reason SDL_PollEvent hangs for exactly 1 minute each iteration. This is currently blocking our development.

I have set up a very basic project which produces the bug on my machine. If any further information is required please let me know.
Comment 1 jannesdrijkoningen 2019-02-02 00:29:54 UTC 
Created attachment 3591 [details]
Bare Project

Seems like the attachment was too big, removed .vs folder.
Comment 2 Ryan C. Gordon 2019-07-30 17:49:38 UTC 
(Sorry if you get several emails like this, we're marking a bunch of bugs.)

We're hoping to ship SDL 2.0.11 on a much shorter timeframe than we have historically done releases, so I'm starting to tag bugs we hope to have closed in this release cycle.

Note that this tag means we just intend to scrutinize this bug for the 2.0.11 release: we may fix it, reject it, or even push it back to a later release for now, but this helps give us both a goal and a wishlist for the next release.

If this bug has been quiet for a few months and you have new information (such as, "this is definitely still broken" or "this got fixed at some point"), please feel free to retest and/or add more notes to the bug.

--ryan.
Comment 3 Daniel Gibson 2019-07-30 18:29:49 UTC 
Might be worth trying if it's fixed with SDL 2.0.10 - maybe this once again is related to that Windows HID thing (#4389)
Comment 4 Ryan C. Gordon 2019-09-20 20:47:38 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 5 Ryan C. Gordon 2019-09-20 20:48:38 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 6 Sam Lantinga 2019-09-22 22:38:36 UTC 
Can you recheck this with the SDL 2.0.10 release?

Thanks!
Comment 7 jannesdrijkoningen 2019-09-23 21:13:36 UTC 
Hello Sam,

I just downloaded the attachment, replaced SDL with the latest version, and can no longer reproduce the bug. It seems to be fixed! :)

Regards,
Jannes.
Comment 8 Sam Lantinga 2019-09-24 02:44:38 UTC 
Great, thanks!