You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I verified this when profiling the application using VS 2019 on Windows 10, with most of the cpu time being spent in the PollEvent function. Following some suggestions in the comments I downgraded to 2.0.8 and the issue was resolved.
I only tested versions 2.0.9 and 2.0.12 and noticed that the issue is still present.
On 2020-06-04 05:28:13 +0000, Cameron Gutman wrote:
Do you have sample code that reproduces the issue?
Can you post your profiling results?
SDL_PollEvent() is going to be hot in profiles, especially if called in a tight loop like that, because that's where most of the event handling logic of SDL takes place. To get deeper than just SDL exports in your profile, you'll probably need to build SDL2.dll locally to ensure the PDB is available for the profiler.
On 2020-06-04 20:07:54 +0000, Carlos Tobon wrote:
Created attachment 4370
Screen of profiling on SDL 2.0.12
On 2020-06-04 20:08:42 +0000, Carlos Tobon wrote:
Created attachment 4371
Screen of profiling on SDL 2.0.8
On 2020-06-04 20:14:31 +0000, Carlos Tobon wrote:
Hope this gives a better picture. Unfortunately this is what I can manage atm without building from src.
If need be, I will try and see if I can do that over the weekend. Just want to point out that it becomes really fast when using 2.0.8 with no changes in the logic. and is broken from 2.0.9 and up.
On 2020-06-07 01:58:28 +0000, Cameron Gutman wrote:
Unfortunately, without symbols for SDL it's impossible to determine from the profiling data where the problem is inside SDL_PollEvent().
Fortunately, SDL has pre-made VS projects which make it pretty simple to build.
On 2020-06-07 02:30:16 +0000, Carlos Tobon wrote:
You're right, it was easy to build the project with the pdb. Just wanted to point out that in my particular scenario, I am using the c# bindings as well.
Even with the pdbs for the bindings and SDL, I am not currently seeing any additional info when profiling. I do see that the symbols are being loaded. Do you have any other suggestions?
On 2020-06-07 03:00:29 +0000, Carlos Tobon wrote:
Created attachment 4374
More profile info
Additional profiling info
On 2020-06-07 03:02:38 +0000, Carlos Tobon wrote:
Please see the latest attachment as I was able to drill down and it looks to be an issue with the GetClipCursor() in WIN_UpdateClipCursor(). Let me know if you need any other additional info.
This is a deal breaker for me and many other people being forced to downgrade to SDL 2.0.8 again if they want to use relative mouse mode or mouse grab without performance issues.
On 2020-08-09 11:31:06 +0000, Dave Lawrence wrote:
Hi,
We are seeing occasional unexpected 'long' pauses in SDL_PollEvent, we added a very basic timer around the call to try and catch these, reporting execution times longer than 10ms, here's a short snippet of output:
This bug report was migrated from our old Bugzilla tracker.
These attachments are available in the static archive:
Reported in version: 2.0.12
Reported for operating system, platform: Windows 10, x86_64
Comments on the original bug report:
On 2020-06-01 14:18:37 +0000, Carlos Tobon wrote:
On 2020-06-04 05:28:13 +0000, Cameron Gutman wrote:
On 2020-06-04 20:07:54 +0000, Carlos Tobon wrote:
On 2020-06-04 20:08:42 +0000, Carlos Tobon wrote:
On 2020-06-04 20:14:31 +0000, Carlos Tobon wrote:
On 2020-06-07 01:58:28 +0000, Cameron Gutman wrote:
On 2020-06-07 02:30:16 +0000, Carlos Tobon wrote:
On 2020-06-07 03:00:29 +0000, Carlos Tobon wrote:
On 2020-06-07 03:02:38 +0000, Carlos Tobon wrote:
On 2020-06-07 07:05:13 +0000, Dom wrote:
On 2020-06-10 04:48:42 +0000, Sam Lantinga wrote:
On 2020-06-10 12:07:15 +0000, Carlos Tobon wrote:
On 2020-08-09 11:31:06 +0000, Dave Lawrence wrote:
The text was updated successfully, but these errors were encountered: