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 4336 - SDL going into fullscreen during a Windows 10 RDP session crashes the SDL library
Summary: SDL going into fullscreen during a Windows 10 RDP session crashes the SDL lib...
Status: NEW
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: 2.0.8
Hardware: x86_64 Windows 10
: P2 major
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-27 10:53 UTC by superfury
Modified: 2018-10-27 10:53 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description superfury 2018-10-27 10:53:58 UTC 
I notice that the entire desktop becomes unresponsive(verified using both Windows 10 RDP and TeamViewer). Visual Studio Community 2018 breaks into it's debugger(being unresponsive itself).

(replace APP_NAME.exe with the SDL app's filename.
It says: "Exception thrown at 0x0000000000000000 in APP_NAME.exe: 0xC0000005: Access violation executing location 0x0000000000000000.

The debugger itself looks like it's pointing to SDL_render_GL.c line 1093.

The entire desktop is unreponsive. The only thing that can be done is CTRL+ALT+END to log off. Any other actions(like task manager) show the task manager which is also unresponsive, probably due to SDL still being in fullscreen somehow.