Skip to content
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

Terminals render gobbled text in VSCode (browser) on gitpod.io #4483

Open
geropl opened this issue Apr 19, 2023 · 2 comments
Open

Terminals render gobbled text in VSCode (browser) on gitpod.io #4483

geropl opened this issue Apr 19, 2023 · 2 comments

Comments

@geropl
Copy link

geropl commented Apr 19, 2023

When using terminals on gitpod.io, sometimes the rendering of terminals is broken, and looks like this:
image
(Notice the blank areas. Sometimes it shows gobbled characters instead)

When selecting some text in the terminal, it renders correctly though, so the buffer itself seems fine.

This problem is sticky to the tab:

  • reload does not help, nor does stop/starting the workspace
  • closing the tab, and opening the same (running) workspace in a fresh tab fixes it ✔️

Happy to provide more input, but not sure what would help in this case! 🙏

Potentially related: #3600

Details

  • Browser and browser version: Firefox 112.0 (64-bit)
  • OS version: Linux Mint 20.3 Cinnamon / 5.4.0-144-generic
  • xterm.js version: how to obtain?
  • VSCode version: 1.77.3

Steps to reproduce

  1. Start some workspaces on gitpod.io, using "VSCode Browser"
  2. Repeat until you hit one with broken terminals (seems to be around a 10% chance)
@jerch
Copy link
Member

jerch commented Apr 28, 2023

Hmm, this indeed needs more info/testing on your side to get down to the issue behind.

Can you repro this on the xterm.js demo with your system? Problem here is the indirection with gitpod --> vscode in between before getting to xterm.js mechs, which adds complexity and more potential "issue surface".

2. Repeat until you hit one with broken terminals (seems to be around a 10% chance)

Does this only happen for late terminals? Like it is never happening for the early ones? Because there might be a chance that you run into context creation issues by the browser engine for the renderer. With which renderer do see this? If its only webgl, then maybe your engine runs out of gl contexes, if it also happens with the canvas renderer, then maybe there is something wrong with the char atlas.

Maybe related: #4480, #4379

I doubt that this one is related to #3600, as this is mostly because of keyboard issues under android.

@Tyriar
Copy link
Member

Tyriar commented May 2, 2023

This could be fixed in gitpod with microsoft/vscode#181359?

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

No branches or pull requests

3 participants