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
This happens where SDL_PollEvent calls WIN_CheckICMPProfileChanged somewhere in it's execution path.
This triggers the Visual Studio debugger somehow (don't know what causes it, it looks like something during a RDP disconnect after the app is started without RDP if I see it happening correctly).
So far crashed my app twice already in the long runs of running it (performing a long testing process of an slow OS installation inside it).
The text was updated successfully, but these errors were encountered:
Somehow, this prevents crashing the SDL2 app, but after disconnecting RDP screen updates fail (as in screen not updating changed pixels rendered by the app) if RDP is connected again without the local machine (non-RDP or other remote control software) logging on the machine.
If after disconnecting RDP another connection is made without logging back into the user (it's at the lock screen because of the first RDP connect) either from the real machine inputs(mouse/keyboard) or other remote control software (non-RDP), the RDP that's starting won't render updates to the window anymore.
Steps to reproduce:
Run app from non-RDP and connect RDP, or connect RDP and run the app.
Disconnect RDP.
Log back in without RDP.
Connect RDP.
If step 3 isn't done, after step 4 the window fails to update changes to it's pixels by SDL2.
This continues(steps 2-4) until step 3 is performed. After step 4, step 2-4 still applies until the app/window is closed (which restarts from step 1 when relaunching etc.).
This happens where SDL_PollEvent calls WIN_CheckICMPProfileChanged somewhere in it's execution path.
This triggers the Visual Studio debugger somehow (don't know what causes it, it looks like something during a RDP disconnect after the app is started without RDP if I see it happening correctly).
So far crashed my app twice already in the long runs of running it (performing a long testing process of an slow OS installation inside it).
The text was updated successfully, but these errors were encountered: