blank proxy popup window

[chrisrosko]

When I start VSCode 1.49.0 the proxy authentication window pops up, but is completly blank (see picture below).

• VSCode Version: 1.49.0 (e790b93 2020-09-10T13:22:08.892Z)
• OS Version: Windows_NT x64 10.0.17763

The same happens with VSCode-Insiders 1.49.0 f66741d 2020-08-31T05:32:36.938Z

It worked with a privious version:
Version: 1.45.0-insider
Commit: 4f05de8
Date: 2020-04-13T17:53:50.995Z
Electron: 7.2.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.17763

[chrmarti]

Could be #106434. Could you check the latest Insiders build (cca20eb from 9/12 or later)?

[chrisrosko]

Could be #106434. Could you check the latest Insiders build (cca20eb from 9/12 or later)?

Sure.

[chrisrosko]

Could be #106434. Could you check the latest Insiders build (cca20eb from 9/12 or later)?

I tested cca20eb and the error is still there.

[bpasero]

I cannot reproduce with latest insiders:

I followed the steps from #106489 (comment) on Windows.

Also, the blank window should not happen as a result of #106434. If you hit #106434 you will see the dialog closing immediately.

Is there any output when you run code-insiders --verbose and follow these steps that you could attach?

[chrisrosko]

verbose.txt

This is the output I get with --verbose.

[bpasero]

@zr0395 is that the full output from the command line? I am missing specific output from the windows itself, they should start with something like this: [16237:0915/093259.345021:INFO:CONSOLE(1705)]

The reason I ask is because I wonder if the auth dialog that opens throws an error. To clarify, you never see the controls to type username and password right?

[chrisrosko]

I will check again, give me a second.

Yes that right.

[chrisrosko]

okay it looks like I found the error. I was starting vscode from a network drive.
I copied it to my lokal drive and started it and the proxy authentication worked.

Anyways I didn't find the output in the main log you discribed.

[bpasero]

@joaomoreno fyi this maybe unrelated and could point to an issue with supporting the auth dialog from network drives. Though checking the code it seems we load the window like other windows and if something was going wrong with how we compute paths it would probably fail for the workbench too.

I added network drive support to #106489

[bpasero]

Hmmmmmm, something that we only seem to be doing for our normal renderers is this, so I wonder if this was always broken:

vscode/src/bootstrap-window.js

Line 247 in 836fbb1

if (safeProcess.platform === 'win32' && pathName.startsWith('//')) { // specially handle Windows UNC paths