Skip to content

Improve handling of webgl context loss #120393

Closed

Description

@Tyriar

We should adopt xtermjs/xterm.js#3276. An easy fix is to just fallback when this happens, we need to make sure we don't save suggested renderer type if the webgl renderer is good though.

Activity

  1. added
    bugIssue identified by VS Code Team member as probable bug
    terminalGeneral terminal issues that don't fall under another label
    on Apr 2, 2021
  2. added
    unreleasedPatch has not yet been released in VS Code Insiders
    insiders-releasedPatch has been released in VS Code Insiders
    and removed
    unreleasedPatch has not yet been released in VS Code Insiders
    on Apr 2, 2021
  3. connor4312 commented on Apr 29, 2021

    @connor4312
    Member

    Can you add verification steps?

  4. meganrogge commented on Apr 29, 2021

    @meganrogge
    Collaborator

    To verify:

    Context loss is achieved at a diff't limit for each computer.

    Using VS code stable - create as many terminals as needed to trigger context loss. When you reach that state, you'll see context loss

    Now in Insider's, create the same number of terminals. You shouldn't see any of those context loss images.

  5. connor4312 commented on Apr 29, 2021

    @connor4312
    Member

    very nice, I like how the fallback magically works

  6. locked and limited conversation to collaborators on May 17, 2021
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 buginsiders-releasedPatch has been released in VS Code InsidersterminalGeneral terminal issues that don't fall under another labelterminal-renderingverifiedVerification succeeded

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions