Flow: Flow 0.69 on Windows keeps crashing (all the time)

[lll000111]

I'm use to very frequent Flow crashes, but this is unusable, I have to go back to 0.68. Even just starting WebStorm (which starts a Flow server) without doing anything at all apart from switching to the Flow console panel to see how the spawned Flow server is doing shows a loooong list of crashes (restart attempt followed by another crash). From the command line too I get unusable behavior.

Flow 0.69, Windows 10

Mar 29 10:14:46.879 [error] Closing connection 'some ephemeral connection' due to uncaught exception in read loop: Unix.Unix_error(Unix.ECONNRESET, "write", "")
Mar 29 10:14:46.879 [error] backtrace:
Mar 29 10:14:46.879 [error] Raised by primitive operation at file "src/unix/lwt_unix.cppo.ml", line 648, characters 38-65
Mar 29 10:14:46.879 [error] Called from file "src/unix/lwt_unix.cppo.ml", line 501, characters 13-24
Mar 29 10:14:46.879 [error] Re-raised at file ".\src\monitor\connections\flowServerMonitorConnection.ml", line 152, characters 6-230
Mar 29 10:14:46.879 [error] 

Overall 0.69 behaves WORSE than 0.68, it hangs, right now for example in

Please wait. Server is garbage collecting shared memory: -

It is only a 10,000 LoC project and it always was done within seconds. Now it keeps "re-crashing" and never getting better, and it keeps hanging with various messages idling forever, like the above. I have to manually call flow stop and restart it.

[OutThisLife]

Getting this as well.

[pgunsolley]

Same.

I'm not sure if my problem is completely identical, as I get a variety of errors whenever flow crashes.

I realized you can force it to somewhat 'reset' by running it again with an empty .flowconfig, and then running it again with your settings. I wrote a bit of code for my environment (grunt). It doesn't work 100% of the time; just more often than not. Maybe you can adopt a similar solution for your environments:

grunt.registerTask('reset-flow', function() {
    let 
    fs = require('fs'),
    exec = require('child_process').exec,
    file = './.flowconfig',
    contents = fs.readFileSync(file)
  ;
  fs.writeFileSync(file, '');
  exec('flow');
  fs.writeFileSync(file, contents);
});`

EDIT: Looks like this doesn't even work for me anymore

[coder2000]

Still getting this with 0.86
flow.log

[jamesisaac]

@coder2000 Do you think this could be related to https://github.com/facebook/flow/issues/7512#issuecomment-470675612 ? Does it still crash if you have nothing under [include]?

[Aziaev]

I have same issue on Windows 10 with WebStorm. Flow doesn't highlights type errors in code

[madeleinemf]

Similar to @Aziaev - I am having endless crashing of the flow server in Pycharm. It either crashed and fails to display any type errors. Or it crashes so badly that Pycharm completely dies and I have to kill it. It also seems to be leaking flow.exe processes all over the place...

[vomatec]

Same problem here on Windows 10 and WebStorm 2019.2.
Starting flow servers all the time. They crash almost immediately. Flow stops type checking after a timeout is reached. No flow servers getting started anymore.