-
Notifications
You must be signed in to change notification settings - Fork 28.4k
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
Cannot open Visual Studio Code when Offline (no internet connection) #18507
Comments
Please provide some additional information here to help us investigate. VSCode normally works fine offline |
@thanhcuong90 without additional information we can't investigate the issue. Will reopen the issue when additional information is provided. |
I am able to reproduce this. Fresh copy of Visual Studio Code and attempt to run on a machine that is disconnected from internet access results in screen appearing but the application hangs completely. Tested on Windows Server 2012R2. CPU is spiked to 100% by the Visual Studio Code process. |
@BSykesUSCG can you provide the command line of the Visual Studio Code process that has 100% CPU load? |
Reproduced on two separate machines at my location. "XXXXXX\DotNet\VSCode-win32-1.8.1\Code.exe" --type=renderer --no-sandbox --primordial-pipe-token=F436D4581BC6D17D9CAF6C3BC8C960F2 --lang=en-US --app-user-model-id=Microsoft.VisualStudioCode --node-integration=true --background-color=#1E1E1E --enable-pinch --device-scale-factor=1 --num-raster-threads=1 --content-image-texture-target=3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553 --video-image-texture-target=3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553,3553 --disable-accelerated-video-decode --disable-webrtc-hw-encoding --disable-gpu-compositing --mojo-channel-token=33C3A637ADC8A62D808730F7AD405879 --mojo-application-channel-token=F436D4581BC6D17D9CAF6C3BC8C960F2 --channel="3892.0.407487230\289126489" --mojo-platform-channel-handle=1584 /prefetch:1 No Visual Studio Code |
@bpasero @joaomoreno any idea what could cause this? |
Looks to me like #7570 which however I was never able to reproduce. @thanhcuong90 can you try to start Electron on that setup? I wonder if it starts (https://github.com/electron/electron/releases/download/v1.4.15/electron-v1.4.15-win32-ia32.zip) |
@BSykesUSCG can you try @bpasero test #18507 (comment) as well? |
Running electron appears to work without issues. Just starting the exe (double-click) brings up the window and it is responsive. |
Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: http://code.visualstudio.com/Download#insiders |
It appears to exhibit the same behavior. Additional detail: If I use task manager to lower the cpu priority on the thread that is eating all the CPU to low I am able to access the menu and window normally. Other than that things are very limited. The window itself is black inside the border and menus generally don't do anything. The exception seems to be the Help->About and Help->Toggle Developer Tools which both do come up. |
@BSykesUSCG is there any output in the "Console" when you open "Developer Tools"? Could you start a profiling session to capture where most time is spend? To create a CPU profile using developer tools in VS Code:
|
Ok, get this.... Open up, start the profile and wait 20 sec. Hit the stop button and it hangs for what I'm betting was an additional 60 sec. It finally completes, the trace comes up and the CPU load drops off and the app LOADS finally...... The trace is 16MB unzipped |
I wonder if this is Windows Server 2012 related. Any chance you could test on a different OS? |
Yep, it works fine on a 2008R2 box. So its either the OS difference or some security tool that we have installed that is different between the machines. Its odd though because I left the app running on the 2012R2 box for more than an hour and it does not come up until you follow the process I described above. Its flipping some bit somewhere that lets it "pass" whatever is causing the CPU spike. |
I suggest we continue in #7570 |
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: