Pylint processes STILL eat all memory (#8503 was wrongly closed)

[gatopeich]

Issue Type: Bug

Issue #8503 still happens on latest version, please reopen it.
Sorry @sevdog, I only found about your response when the issue hit me again!

Extension version: 2020.1.58038
VS Code version: Code 1.41.1 (26076a4de974ead31f97692a0d32f90d735645c0, 2019-12-18T15:04:31.999Z)
OS version: Linux Mint 19 / Ubuntu 18.04 / Linux x64 4.15.0-72-generic
Python version: 3.7.5-2~18.04

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (8 x 3456)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: unavailable_off rasterization: disabled_software skia_renderer: disabled_off surface_control: disabled_off surface_synchronization: enabled_on video_decode: unavailable_off viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off webgl: enabled webgl2: enabled
Load (avg)	0, 1, 1
Memory (System)	31.31GB (7.29GB free)
Process Argv	--no-sandbox --unity-launch
Screen Reader	no
VM	0%

[brettcannon]

Unfortunately Pylint memory usage is not directly under our control.

Closing as a duplicate of #4236 as that's the best option for solving this.

[gatopeich]

Not a pylint issue.
#8503 was accidentaly closed and LOCKED so I had to open the same issue here.

#8503 should be reopened!

Unfortunately Pylint memory usage is not directly under our control.

Closing as a duplicate of #4236 as that's the best option for solving this.

[brettcannon]

I'm sorry but shouting is not going to help your case with this.

#4236 or #3836 are going to be how we would solve this. If you would like to see this resolved you can upvote either issue to help raise their importance.