flow is crashing on windows system
abdullah-aj opened this issue · 2 comments
When I try to run flow on windows it crashes with a weird error Unix.Unix_error(Unix.ENOTSOCK, "select", "")
node --version
v15.9.0
npm --version
7.5.3
Operating System
Windows 10 Pro 64bit
Build 20H2
Steps to Error
npm init
npm i -D flow-bin
add flow to script in package.json
npm run flow init
npm run flow
ERROR
Error Details
PowerShell Screenshot
Logs
[2021-02-24 03:44:28.921] argv=E:\LearningLab\Work\TechnicianApp\node_modules\flow-bin\flow-win64-v0.135.0\flow.exe start --flowconfig-name .flowconfig --temp-dir C:\Users\ajplu\AppData\Local\Temp\flow E:\LearningLab\Work\TechnicianApp
[2021-02-24 03:44:28.921] lazy_mode=off
[2021-02-24 03:44:28.921] arch=types_first
[2021-02-24 03:44:28.921] abstract_locations=off
[2021-02-24 03:44:28.921] max_workers=4
[2021-02-24 03:44:28.921] debug=false
[2021-02-24 03:44:28.922] Initializing Server (This might take some time)
[2021-02-24 03:44:28.922] executable=E:\LearningLab\Work\TechnicianApp\node_modules\flow-bin\flow-win64-v0.135.0\flow.exe
[2021-02-24 03:44:28.923] version=0.135.0
[2021-02-24 03:44:28.923] No saved state available
[2021-02-24 03:44:28.924] Parsing
Monitor died unexpectedly
Monitor Logs
Feb 24 03:44:28.796 [info] argv=E:\LearningLab\Work\TechnicianApp\node_modules\flow-bin\flow-win64-v0.135.0\flow.exe start --flowconfig-name .flowconfig --temp-dir C:\Users\ajplu\AppData\Local\Temp\flow E:\LearningLab\Work\TechnicianApp
Unix.Unix_error(Unix.ENOTSOCK, "select", "")
Raised by primitive operation at file "src/common/lwt/lwtInit.ml", line 36, characters 18-46
Called from file "list.ml", line 117, characters 24-34
Called from file "src/common/lwt/lwtInit.ml", line 34, characters 8-206
Called from file "src/unix/lwt_engine.ml", line 344, characters 8-19
Called from file "src/unix/lwt_main.ml", line 33, characters 4-78
Called from file "src/common/lwt/lwtInit.ml", line 129, characters 4-135
Called from file "src/hack_forked/utils/sys/daemon.ml", line 150, characters 4-20
Any help would be highly appreciated!!
Found this reason.
It turned out somehow Astril VPN was causing flow server to crash. even though it was only installed and not running. After uninstalling Astril flow works like a charm.
If someone encounters a similar problem, then they should try to uninstall their VPN/Proxy software. I am not sure if other VPN software can cause this issue because I have only used Astril.
but why does it have a conflict with astril? why does it give such a weird error message?
Thanks for following up when you found a workaround. This is indeed very strange. I'm not really (at all) familiar with Windows but I wonder if Astril is somehow intercepting Winsock APIs and interfering with flow's socket.
Anyway, this repository is just packaging prebuilt binaries. Please report issues with Flow itself on facebook/flow