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

Visual Studio Codium turns blank when alt-tabbing to other maximised windows. #312

Closed
2 tasks done
ghost opened this issue Jan 2, 2020 · 6 comments
Closed
2 tasks done
Labels
bug Something isn't working

Comments

@ghost
Copy link

ghost commented Jan 2, 2020

Describe the bug
VSCodium randomly goes blank when I switch to Discord, Chrome or any other window that is maximised. Have to open a new instance to get a display again.

Please confirm that this problem is VSCodium-specific

  • This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

Screenshots
Screenshot

Desktop (please complete the following information):

  • OS: Windows 10
  • Architecture: x64
  • Version: 1.41.1

Additional context
I'm still able to click buttons but I can not see them.

@ghost ghost added the bug Something isn't working label Jan 2, 2020
@stripedpajamas
Copy link
Member

Potentially a duplicate of #296 ?

@ghost
Copy link
Author

ghost commented Jan 2, 2020

Potentially a duplicate of #296 ?

I provided a lot more information, plus it isn't related to the amount of windows open on my desktop but instead the fact I'm switching between windows that are maximised. Haven't tested with windowed applications.
Edit: I read that one first before posting this and I'm quite sure it isn't the same issue. If it is I pardon the inconvenience.

@theianrey
Copy link

Same here. Currently experiencing this issue with the same specs. I need to re-open codium just to make it work again. But still, after re-opening, the issue persist after some time it was being open.

@ghost
Copy link
Author

ghost commented Jan 5, 2020

I'm still awaiting an update on the status of the issue. I don't truly recognise what is happening in the code so I can't make a fork and make a hotfix. I'll try to work on it but not sure how much progress I'll make.

@theianrey
Copy link

I'm still awaiting an update on the status of the issue. I don't truly recognise what is happening in the code so I can't make a fork and make a hotfix. I'll try to work on it but not sure how much progress I'll make.

just fire some updates whenever you have any findings.
thanks.
😄

@stripedpajamas
Copy link
Member

@simplyahydra @theianrey is this still happening on 1.47.x or 1.48.x ?

@daiyam daiyam closed this as completed Sep 6, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants