VS Code UI broken in Mojave VM

M

MichaelD32

Junior Member
Running the trial Parallels 14 for Mac in an effort to build a dev environment. Stuck at Visual Studio code. Mojave installed fine. VS Code 1.27.2 on it has a broken UI and is not usable.
What can I do to fix this?
 
Sort by date Sort by votes
SOLUTION: I found a video over on Youtube that gives a simple solution for the video glitch that occurs with VS Code on a macOS guest OS. The answer is to turn off the GPU for VS Code.
TL;DR Create a one-line shell script (below) then make it executable. The video shows how... Script is:
open /Applications/Visual\ Studio\ Code.app --args --disable-gpu
Here is the Youtube Video:
 
Upvote 0 Downvote
HEY PARALLELS! I can't believe you're just ignoring this post! IS THERE GOING TO BE FIX FOR ELECTRON APPS RUNNING PARALLELS, in Windows running on a MacOSX Host? THIS IS INCREDIBLY IMPORTANT. Slack doesn't work either!!!
 
Upvote 0 Downvote
prenez said:
HEY PARALLELS! I can't believe you're just ignoring this post! IS THERE GOING TO BE FIX FOR ELECTRON APPS RUNNING PARALLELS, in Windows running on a MacOSX Host? THIS IS INCREDIBLY IMPORTANT. Slack doesn't work either!!!
Click to expand...
Hi, please sorry for the any inconvenience caused. Please provide us with the detailed description: what exactly doesn't work, did you get any error message.
Also please collect the tech report once the issue reproduced and post the report's ID here.
 
Upvote 0 Downvote
Maria@Parallels said:
Hi, please sorry for the any inconvenience caused. Please provide us with the detailed description: what exactly doesn't work, did you get any error message.
Also please collect the tech report once the issue reproduced and post the report's ID here.
Click to expand...

Thanks to Rich above, yes "open /Applications/Visual\ Studio\ Code.app --args --disable-gpu" does work for me, and in all recent OSX versions (including Calatina). This is for all Electron apps I use, and a workaround for chrome in another thread.

I think the point people are making though, is that the workaround to disable the GPU by running a terminal command is what we would like to be looked at, its been an issue experienced for years (I've posted in another thread a while back also).
 
Upvote 0 Downvote
You must log in or register to reply here.
Back
Top