Skip to content

Terminal canvas context loss is not handled #94513

Closed as not planned
Closed as not planned

Description

@kzhui125
  • VSCode Version: 1.43.2
  • OS Version: macOS 10.15.4

2

Activity

  1. Tyriar commented on Apr 6, 2020

    @Tyriar
    Contributor

    Upstream issue: issues

  2. added
    bugIssue identified by VS Code Team member as probable bug
    terminalGeneral terminal issues that don't fall under another label
    upstreamIssue identified as 'upstream' component related (exists outside of VS Code)
    upstream-issue-linkedThis is an upstream issue that has been reported upstream
    on Apr 6, 2020
  3. added this to the Backlog milestone on Apr 6, 2020
  4. changed the title [-]VSCode Terminal crash[/-] [+]Terminal canvas context loss is not handled[/+] on Apr 6, 2020
  5. Tyriar commented on Jul 16, 2021

    @Tyriar
    Contributor

    Actual issue link: xtermjs/xterm.js#2816

  6. Tyriar commented on Oct 11, 2021

    @Tyriar
    Contributor

    I believe this is handled now for webgl with xtermjs/xterm.js#3276

  7. meganrogge commented on Oct 11, 2021

    @meganrogge
    Collaborator

    closing as this is fixed
    recording - 2021-10-11T110336 453

  8. Tyriar commented on Oct 11, 2021

    @Tyriar
    Contributor

    Megan Rogge (@meganrogge) I think it's still a problem with the canvas renderer? Webgl is only restricted by the canvas count.

  9. anthonykim1 commented on Oct 8, 2026

    @anthonykim1
    Contributor

    🤖 Thanks for the report. This is now fully addressed on current VS Code:

    • The canvas renderer was removed entirely from the terminal (6cdd364).
    • WebGL context loss is handled gracefully — when the GPU reclaims the context, VS Code disposes the WebGL renderer and falls back to the DOM renderer.
    • The upstream xterm.js issue (Handle general canvas context loss xtermjs/xterm.js#2816) is also closed.

    Closing as resolved. If you still see rendering issues after context loss on a recent build, please open a new issue with steps to reproduce.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugIssue identified by VS Code Team member as probable bugterminal-renderingupstreamIssue identified as 'upstream' component related (exists outside of VS Code)upstream-issue-linkedThis is an upstream issue that has been reported upstream

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions