-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle general canvas context loss #2816
Comments
I believe this is handled now for webgl with #3276 |
@Tyriar Is that issue also behind those funky outputs after a machine wakeup from sleep mode for the canvas renderer? If so, is there a way to detect it programmatically like |
@jerch we can't detect that happening on the web, the GPU's texture gets corrupted but AFAICT there's no way for us to listen for it. The fix there in VS Code was to listen via electron to OS resume and clear all texture atlases using the webgl API and the new xterm core API for clearing the canvas texture atlas. |
Hmm ic, well its a pity but not much we can do about it. |
Contexts can become lost when graphics card drivers are reinstalled for example. This should be handled generically.
VS Code issue: microsoft/vscode#94513
Related: #2253
The text was updated successfully, but these errors were encountered: