Update g.xlf -> EMFILE: too many open files

[MarkDeBeerV]

Issue Type: Bug

Describe the bug
I start update g.xlf in my app. This has always worked fine till now. There 108 al files in the app.

To Reproduce
Steps to reproduce the behavior:

1. Open the app (with 108 al files)
2. run update g.xlf
3. see the error Update g.xlf failed with error: EMFILE: too many open files, open 'c:...\app.json'

• Does it happen all the time?
  yes.

• Did it used to work?
  yes, I just added some files again however.

Extension version: 1.26.0
VS Code version: Code 1.68.1 (30d9c6cd9483b2cc586687151bcbcd635f373630, 2022-06-14T12:48:58.283Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz (12 x 2712)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	15.73GB (3.99GB free)
Process Argv	--crash-reporter-id 2ff971e1-15be-4ff7-9546-12bf20075a8e
Screen Reader	no
VM	0%

A/B Experiments

vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonvspyt551:30345470
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
vsclangdf:30486550

[MarkDeBeerV]

A restart of Visual Studio helped...

[jwikman]

Hi @MarkDeBeerV,

This is so strange... I can see in the telemetry that this has happened a few times the last month (like on 5 occasions), but several times repeatedly when it happens. Probably until restart of VSCode as you did now.

We will need to figure out a way to hunt this bug down... But at least it seems as if we're not alone, according to google. :)

But the workaround for now, is as you already discovered: Developer: Reload Window