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.

Sign up for GitHub

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

Jump to bottom

v1.50.1 creates debug.log automatically #108886

Closed
theS1LV3R opened this issue Oct 18, 2020 · 13 comments
Closed

v1.50.1 creates debug.log automatically #108886

theS1LV3R opened this issue Oct 18, 2020 · 13 comments
Assignees
@deepak1556
Labels
info-needed Issue requires more information from poster windows VS Code on Windows issues

Comments

@theS1LV3R
Copy link

Issue Type: Bug

  1. Open a folder
  2. Open any file in said folder

VSCode will automatically create a debug.log file. This issue was not present on v1.50, but appeared on v1.50.1.

Related: #105191. (Bug was fixed on v1.49.2, has now reappeared again). Repro steps from that issue are likely to work now too.

VS Code version: VSCode 1.50.1 (d2e414d, 2020-10-15T10:44:06.171Z)
OS version: Windows_NT x64 10.0.19041

System Info
Item Value
CPUs Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8 x 2112)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: enabled_on
protected_video_decode: enabled
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 7.84GB (0.77GB free)
Process Argv
Screen Reader no
VM 0%
Extensions (47)
Extension Author (truncated) Version
better-comments aar 2.1.0
html-snippets abu 0.2.1
vscode-sqlite ale 0.9.0
bracket-pair-colorizer-2 Coe 0.2.0
vscode-markdownlint Dav 0.37.1
vscode-eslint dba 2.1.10
githistory don 0.6.12
gitlens eam 10.2.2
EditorConfig Edi 0.15.1
vscode-npm-script eg2 0.3.13
vscode-front-matter eli 1.7.0
prettier-vscode esb 5.7.1
vs-code-xml-format fab 0.1.5
vscode-npm fkn 3.3.0
ginfuru-vscode-jekyll-syntax gin 0.1.1
vscode-jekyll-snippets gin 0.9.3
gc-excelviewer Gra 3.0.40
Python-autopep8 him 1.0.2
vue-snippets hol 0.1.12
svg joc 1.3.11
docthis joe 0.7.1
vsc-python-indent Kev 1.11.0
kite kit 0.129.0
restructuredtext lex 129.0.0
template-string-converter meg 0.1.8
code-beautifier mic 2.3.3
dotenv mik 1.0.1
vscode-docker ms- 1.6.0
python ms- 2020.9.114305
remote-wsl ms- 0.50.1
debugger-for-chrome msj 4.12.11
vscode-streamdeck nic 4.1.5
hide-gitignored npx 1.1.0
vetur oct 0.28.0
vscode-versionlens pfl 1.0.8
material-icon-theme PKi 4.3.0
ruby reb 0.27.0
synthwave-vscode Rob 0.1.8
trailing-spaces sha 0.3.1
svg-preview Sim 2.8.3
control-snippets svi 1.9.1
sass-indented syl 1.8.12
html-preview-vscode tht 0.2.5
vscode-icons vsc 11.0.0
vscode-ruby win 0.27.0
markdown-all-in-one yzh 3.3.0
material-theme zhu 3.9.3

(1 theme extensions excluded)
@connor4312 connor4312 assigned deepak1556 and unassigned connor4312 Oct 18, 2020
@deepak1556
Copy link
Contributor

I am unable to repro with the steps from previous issue as well as the current one. We haven't changed the runtime between 1.50 and 1.50.1, so highly unlikely the issue resurfaced. Can you paste the contents of debug.log ?

@deepak1556 deepak1556 added info-needed Issue requires more information from poster windows VS Code on Windows issues labels Oct 18, 2020
@balintbalazs
Copy link

I can confirm this behaviour. The contents of the file:

[1019/095427.124:ERROR:directory_reader_win.cc(43)] FindFirstFile: The system cannot find the path specified. (0x3)

Version: 1.50.1 (user setup)
Commit: d2e414d
Date: 2020-10-13T15:06:15.712Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19041

@theS1LV3R
Copy link
Author

theS1LV3R commented Oct 19, 2020 •
edited

For some reason I can't repro anymore, but here is one of the files it created while i still could repro:

[1018/120034.920:ERROR:registration_protocol_win.cc(103)] CreateFile: Systemet finner ikke angitt fil. (0x2)
[1018/120330.913:ERROR:registration_protocol_win.cc(103)] CreateFile: Systemet finner ikke angitt fil. (0x2)
[1018/120724.633:ERROR:registration_protocol_win.cc(103)] CreateFile: Systemet finner ikke angitt fil. (0x2)

Translated: The system cannot find the file specified

Considering someone else could repro I'll keep the issue open.

@AlphaEndgame
Copy link

AlphaEndgame commented Oct 19, 2020 •
edited

Hello, I can confirm that this issue is still happening on v1.50.1. VSCode keeps creating a debug.log on the root of my working directory with these contents:

[1019/155955.848:ERROR:directory_reader_win.cc(43)] FindFirstFile: The system cannot find the path specified. (0x3)

Version: 1.50.1 (user setup)
Commit: d2e414d
Date: 2020-10-13T15:06:15.712Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.17134

@cDurhamZP
Copy link

I am having the same issue. I've ran as administrator as well.

[1016/093125.450:ERROR:directory_reader_win.cc(43)] FindFirstFile: The system cannot find the path specified. (0x3) [1016/121627.459:ERROR:directory_reader_win.cc(43)] FindFirstFile: The system cannot find the path specified. (0x3)

Version: 1.50.1
Commit: d2e414d
Date: 2020-10-13T15:06:15.712Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19041

@deepak1556
Copy link
Contributor

@balintbalazs @AlphaEndgame @cDurhamZP based on the log, the issue you are facing is from chrome and not vscode please refer to https://bugs.chromium.org/p/chromium/issues/detail?id=1138853 for more info.

@ent3r I am closing this issue, can reopen if there is a repro with vscode, the issue is getting side tracked with unrelated bug from chrome or other chromium related browsers.

@theS1LV3R
Copy link
Author

that would make sense if it wasnt for the fact that i dont have chrome/chromium installed. im guessing since electron is also chromium it goes under that bug?

@cDurhamZP
Copy link

I managed to get the error to go away by removing an extension: JavaScript Debugger (Nightly)

Not sure if correlation or causation, but there it is

@deepak1556
Copy link
Contributor

@cDurhamZP the problem is not the extension but the extension spawning any chromium browser for debugging which would hit the issue I had linked.

im guessing since electron is also chromium it goes under that bug?

@ent3r Depends on what other electron app you might have, if there is a reliable repro it would help.

@theS1LV3R
Copy link
Author

I'll have a look if it appears again, thanks for the quick response

@jmoupah
Copy link

jmoupah commented Oct 27, 2020 •
edited

Hello,

same here with VSCodium 1.50.1 and able to repro while not using Chrome :

  1. clone https://git.spip.net/spip-contrib-extensions/cvt_rechercher.git somewhere on your Windows 10 machine
  2. open this repo in VSCodium
  3. clone https://git.spip.net/spip-contrib-extensions/responsivenav.git somewhere else on your Windows 10 machine
  4. open this 2nd repo in another VSCodium
  5. open the file prive\squelettes\contenu\configurer_responsivenav.html
  6. TADAM !

Maybe it's something about windows access permissions to files/folders ? But don't know why it's not for everye files...

@deepak1556
Copy link
Contributor

@jmoupah VSCodium is not vscode, they wouldn't have the runtime that contains the fix yet.

@jmoupah
Copy link

jmoupah commented Oct 28, 2020

Ok, thanks for your answer.
Thing is, I don't see any issue on the repo https://github.com/VSCodium/vscodium/issues?q=is%3Aissue+debug.log

@jmoupah jmoupah mentioned this issue Oct 28, 2020
Closed
@github-actions github-actions bot locked and limited conversation to collaborators Dec 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@deepak1556 deepak1556

Labels
info-needed Issue requires more information from poster windows VS Code on Windows issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@deepak1556 @connor4312 @AlphaEndgame @jmoupah @theS1LV3R @balintbalazs @cDurhamZP