node.exe / Evented I/O for V8 JavaScript - Processor Cycles Gone Wild

node.exe / Evented I/O for V8 JavaScript - Processor Cycles Gone Wild

LT.Rusty
Advisor Advisor
7,604 Views
29 Replies
Message 1 of 30

node.exe / Evented I/O for V8 JavaScript - Processor Cycles Gone Wild

LT.Rusty
Advisor
Advisor

Anyone else seeing multiple bajillions of instances of node.exe and Evented I/O for V8 JavaScript running and eating all your processor power?  I've been seeing this ever since I upgraded to 2017, and every couple hours I'll have to go in and run a batch file to kill all the node.exe processes, which eases things up for a bit ... but it always comes back.  

 

It seemed at first like it was something connected to Adobe Creative Cloud - according to google, anyway - which confused me because I don't have anything other than Adobe Reader installed on this computer.  I found a couple references to Inventor, though, and something about something-or-other 360 - connected design, maybe? - could have 2 instances of node.exe running, which might cause some issue or other with Inventor.

 

I'm still not positive that it's a problem with Autodesk software here, but I can't seem to find anything other than Adobe or Autodesk where it's used...

 

 

Rusty

EESignature

7,605 Views
29 Replies
Replies (29)
Message 21 of 30

wrw0007
Advocate
Advocate
Thank you for posting this. I am glad I stumbled upon it. I was in the exact same position as you. I have 2016 and 2017 inventor installed, I do not use photoshop and I was seeing on average 12 node.exe processes running and averaging 70% processor use. It was unbearable to say the least. Disabling the tutorials and design share helped, along with taskkilling the processes and restarting. Now I am in a workable environment again, but i am still seeing 9 AcWebBrower.exe processes. Did you ever find out what was going on with that?
0 Likes
Message 22 of 30

wrw0007
Advocate
Advocate
forgot to mention; those 9 AcWebBrowser.exe processes appeared after a fresh restart and opening 1 instance of an inventor project file. No files have been open.
0 Likes
Message 23 of 30

ChrisMitchell01
Community Manager
Community Manager

If you use Task Manager to view the running processes then you can use the column chooser to also show the Command line for each. Post a screenshot & that will enable us to determine what they're for. You likely have 3 for Desktop App, 3 for the Inventor licensing & others TBD.

 

Thanks,
Chris



Chris Mitchell
PDMS Customer Engagment Team
Autodesk, Inc.

0 Likes
Message 24 of 30

wrw0007
Advocate
Advocate
Screenshot should be attached.
0 Likes
Message 25 of 30

wrw0007
Advocate
Advocate
or not... *attempt number 2*
0 Likes
Message 26 of 30

wrw0007
Advocate
Advocate

I forgot the Autodesk Forums hate Mozilla Firefox. Man Mad

acwebstuff.jpg

0 Likes
Message 27 of 30

ChrisMitchell01
Community Manager
Community Manager

All looks correct there. You have 3 for the licensing module (with CLM in the command path), 3 for Desktop App & 3 for the MyHome window in Inventor, (the ones with the full path to Inventor 2017\Bin in the command).

 

You can exit Desktop App & disable MyHome to get rid of 6 of these, but the 3 for licensing will always be there whenever you run a recent Autodesk product.

 

If you're seeing a lot of CPU activity for the ones for MyHome then please ensure you have 2017SP1/R2 installed as there was a MyHome performance fix included there.

 

Hope this helps,
Chris



Chris Mitchell
PDMS Customer Engagment Team
Autodesk, Inc.

Message 28 of 30

LT.Rusty
Advisor
Advisor

Hey, thanks for bringing this up again and reminding me!

 

When the R2 patch was applied, it killed my change to the environment variable, but I haven't seen any recurrences of the original issue I was having at the start of this thread.  Don't know what you did, but it seems to have fixed the problem. 

Rusty

EESignature

0 Likes
Message 29 of 30

wrw0007
Advocate
Advocate
Thanks for the advice and for mentioning the R2 patch. I have it installing as we speak.
0 Likes
Message 30 of 30

wrw0007
Advocate
Advocate
This thread got my average CPU usage down from 70% to 1%. The R2 patch helped a lot and as noted I have not seen the original problem either.
0 Likes