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 3302

Summary: SDL_RenderPresent() DEVICELOST
Product: SDL Reporter: geln <jxw_0017>
Component: renderAssignee: Sam Lantinga <slouken>
Status: RESOLVED ABANDONED QA Contact: Sam Lantinga <slouken>
Severity: critical    
Priority: P2    
Version: 2.0.4   
Hardware: x86   
OS: Windows 7   

Description geln 2016-03-31 08:49:57 UTC 
使用SDL_RenderPresent()渲染时，在本机正常显示，当本机被其他电脑远程连接后，同时将远程窗口最小化后，GetError() 就开始报DEVICELOST的错误，经过初步定为，好像是SDL没有找到正在远程端的硬件加速设备。长时间运行，渲染可能就会不起作用了，没有任何图像显示。
不知道有没有解决方案？
Comment 1 Sam Lantinga 2017-08-12 03:46:22 UTC 
From Google translate:
When using SDL_RenderPresent () rendering, the normal display of the machine, when the machine is connected by other computers, while the remote window is minimized, GetError () began to report DEVICELOST error, after the initial set, as if SDL no Find the hardware acceleration device on the remote side. Long time to run, rendering may not work, and no image display.
Do not know if there is any solution?
Comment 2 Sam Lantinga 2017-08-12 03:48:07 UTC 
When the window is restored DEVICELOST should no longer be reported and you should be able to start rendering normally.

This also shouldn't happen when using the OpenGL renderer, so maybe that is an option instead?
Comment 3 Sam Lantinga 2017-08-12 03:48:41 UTC 
Google translate:
当窗口恢复时，不再报告DEVICELOST，您应该能够正常开始渲染。

这也不应该在使用OpenGL渲染器时发生，所以也许这是一个选项呢？
Comment 4 Ryan C. Gordon 2018-08-06 21:20:21 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.