Flow-for-vscode: flow consumes all ram

[barbalex]

I have described this in these comments:

• https://github.com/facebook/flow/issues/2152#issuecomment-333402410
• https://github.com/facebook/flow/issues/2152#issuecomment-333601924 (and two following)

The weird part is that it completely bombs out my pc when using vscode and flow-for-vscode. But when I use atom, there are no problems.

Could it be that flow-for-vscode is doing something unexpected?

[orta]

i bet the atom version uses flow-language-server: https://github.com/flowtype/flow-for-vscode/pull/150 and so has no need to spawn off the processes itself. You're welcome to try wrap up that PR for this extension.

[barbalex]

Thanks for the pointer. I think I'd bite off a bit too much...

[CharlesStover]

@barbalex I have a similar problem, but specifically Flow is creating dozens of instances of itself to max out RAM.

[caub]

Can confirm, on linux, see the entries with '26GB'

Columns are Command User CPU% RSS VM-Size PID

There might be some memory leak

[willisplummer]

This happens to me too - had to disable the vscode extension

[jinshin1013]

Has there been any active movement on trying to fix this problem?

[indolering]

What about excluding ./**/node_modules/ and JSON or JS files over a certain size by default?

[Mayank1791989]

I am closing this issue as flow has improved a lot (try using new version of flow). Also, this plugin switched to using lsp which will fix plugin spawning lot of processes.