Jump to definition consumes the entire CPU capacity

[lgraziani2712]

Specs:

• Windows 10.
• Atom 1.19.0-beta3
• Hyperclick 0.1.2
• flow-ide 1.6.0

Description

Everytime I try to jump to a definition, this happens:

And my PC freezes. The WMI Provider Host and those bunch of nodejs instances only appear when I try to jump to a definition.

While you try to stabilize this functionality, can you add an option to disable it? Right now I cannot use flow-ide because of that (or I need to be careful not to try to jump to a definition.)

Thank you for your work :)

[steelbrain]

You can disable the hyperclick package to disable jump to definition. You are on windows and Flow on windows was still experimental the last time I checked. Flow architecture has a server that runs in the background and scans the entire project into memory and then clients that query that server. If I am guessing correctly the server is not yet supported on windows and every client tries to scan the entire project by themselves.

Either way, nothing we can do in this package, Flow maintainers will have to fix this in flow :)

[lgraziani2712]

It has a server on windows. And if I'm not wrong, it scans the entire project on init.

[steelbrain]

Regardless, if it jammed the editor, then it would be flow-ide's fault, if it spawns processes and those processes jam the OS then it's those processes' fault.

You could try submitting debug information to the flow repository, people there might be able to help you debug the root cause of this

[lgraziani2712]

What debug information?

How can I generate that information?

Thank you!

[steelbrain]

No idea 😅 The maintainers of flow would know tho

[lgraziani2712]

They told me "The flow binary will show up in windows as flow.exe. This is not a flow issue, it seems as though it is an issue with the plugin you're using."

🙈

[steelbrain]

So next step in debugging, install Process Explorer and try to get the command line arguments of the spawned Node processes that take up all of that CPU

[lgraziani2712]

Wow! I didn't knew about that tool. So good!

The command line is:

node "C:\dev\repos\codimo\node_modules\.bin\\..\flow-bin\cli.js" "get-def" "--json" "C:\dev\repos\codimo\core\blockly\executorGenerator\index.js" "33" "3"

Here is a screenshot

Every process has the same command line.

[Arcanemagus]

Is your project's flow-bin dependency up to date?
Is Node.js up to date?

Normally the Node.js wrapper script should determine the proper flow binary to run, spawn that, and exit itself. For some reason on your machine the wrapper script is never exiting.

In any case, this is an issue with either flow-bin or flow themselves. Check that you are on the latest versions of flow-bin and node first.

[lgraziani2712]

Uhmm, they exit. But spawn a lot of them, more than 20.

Previous versions:

• Node v8.0.0
• flow-bin: v0.50.0

Actual versions:

• Node v8.2.1
• flow-bin: v0.51.0

Still happens. By the way, testing it now, I found that the more time I put the mouse over an element pressing the key to jump to a definition, the more processes spawn.

[steelbrain]

That would only happen if you hold ctrl all the time, do you?

[lgraziani2712]

Uhmm, yes i think. It happens only if I hold ctrl, but the more I hold it, the more processes will be.