Runaway memory use

[JB62]

Issue Type: Bug

Trying to debug certain perl programs, code, or its debug wrapper, sometimes starts to use more and more memory until the machine is swapping wildly, saturating disk io rendering the whole machine unuseable. I can't get much more info as, by definition, the machine stops responding to any user input when this happens. Debugging the same programs with the command-line debugger gives no issues. This isn't specific to one program, but does seem to be more likely to happen when the perl program has structures that need a fair amount of memory in their own right. I appreciate this isn't exactly abundant with detail, but I'm not sure how I can give any more useful info. Sorry.

Extension version: 0.5.0 VS Code version: Code 1.33.0 (0dd516dd412d42323fc3464531b1c715d51c4c1a, 2019-04-04T15:08:57.775Z) OS version: Linux x64 4.4.0-142-generic

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz (8 x 3529)| |GPU Status|2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: disabled_software
surface_synchronization: enabled_on
video_decode: unavailable_off
webgl: enabled
webgl2: enabled| |Load (avg)|0, 0, 0| |Memory (System)|15.63GB (0.45GB free)| |Process Argv|--unity-launch| |Screen Reader|no| |VM|0%|

[hoehrmann]

@JB62: You could enable the debugRaw option in your launch.json. It would show the communication between the extension and the Perl debugger, maybe that gives a clue (e.g., what the last command was). I think vscode also stores the log data as a file, if vscode crashes. The last couple of command to the debugger would be particularily interesting. Also, the cmdline of the process that consumes all the memory would be good to know.

[raix]

This might have been fixed