BUG! Node.js JavaScript Runtime High CPU

[HughesTooling]

Just updated Fusion and on restart Node.js JavaScript Runtime is constant at about 13% (One Core) and CPU is running at max GHz! 

After some tests it seems like the Home start page might be the problem. I have 2 licenses one is the legacy licence with all the Extensions and starts on the home page and as soon as the home page starts to populate Node.js JavaScript Runtime starts and never stops. Using Windows 8.1, will test on Win 10 later.

If I log out and close Fusion, then start using a standard licence with no home start page Fusion starts up fine, Node.js JavaScript Runtime uses a bit of CPU for a minute or so then drops back to pretty much zero. At this point I can log out then back in with the full legacy licence with all the extensions and Fusion runs fine and Node.js JavaScript Runtime is also running correctly but close Fusion and restart and Node.js JavaScript Runtime misbehaves again! So must be something to do with either the home page or all the extensions loading at startup.

Thanks Mark

[matthewZYM62]

Same here. After the update "Node.js JavaScript Runtime" is chewing up the entirety of one CPU core, forever.

[HughesTooling]

@matthewZYM62  I see you're using Win 10? So not an operating system problem. I'm starting to think it's an account problem because I can sign in using a different account and Fusion runs fine. When you sign in using different accounts Fusion creates another UserID and stores preferences .etc separately. I had this happen a couple of months ago and seem to remember it cleared itself after a while, not sure if it was another update or just need to run for hours. @karina.harper  Any ideas? Here's another thread from a few months back, don't think the solution (Graphics Driver) was correct.

Thanks Mark

[matthewZYM62]

Yes, I can confirm this behaviour. When I sign in with my work account (a paid subscription) I see the persistent high CPU from Nodejs. When I sign in with my personal account (a free account) on the same computer there is no problem.

[karina.harper]

@matthewZYM62 

Do you also have the home tab on your work account?

Thanks for tagging me @HughesTooling .

Karina

[matthewZYM62]

I do not.

[HughesTooling]

---

@matthewZYM62 wrote:

Yes, I can confirm this behaviour. When I sign in with my work account (a paid subscription) I see the persistent high CPU from Nodejs. When I sign in with my personal account (a free account) on the same computer there is no problem.

---

@karina.harper  I think this is because there are in effect 2 users when you do this and you have preferences, design cache, .etc separated in the 2 accounts. I have a Win 10 and 8.1 system, the Win 10 setup runs both accounts but the Win 8.1 system has problems with the full legacy account\license. When I have some time I'll try clearing the cache and see if that helps, does that still reset toolbar layout?

If I start with the standard license, sign out (not closing Fusion) then sign in with the full license with all extensions, "Node.js JavaScript Runtime", does not show any problem until I open a design. Then it starts up and just sits at 13.3% in task manager.

Mark

[HarrisonClassic]

I get a similar issue, has been like this for some time.

I do models with CAM.

Exit Fusion, node.exe runs flat out on a single core and never shuts down, see screenshot below. I have to End Task to kill it.

[3d_low]

Similar issue here while trying to open drawings.

This particular drawing took 1 minute to open, not a huge assembly. Opened this drawing in 2 secs right before. In some case the drawings might take over 5 mins to open or not open at all.

Node will oscillate from 6-12% usage while Fusion is trying to open the drawing.

[danijelmil]

Same here, Huge CPU load from NODE.js. Also it stays active with 17-20% load (6th gen i7) after exiting Fusion. Why?

Only basic modeling in Fusion, nothing advanced. One user, one EDU license. 

[WesleyTack]

I too am encountering performance issues. After checking task manager, it is indeed this Node.js. Hopefully something that's known to Autodesk?

[RC-CAD]

This is not only a Widows Problem. I am experiencing the same issue on MacOS 12.6.2 (Monterey). Node will exceed 100% CPU anytime a file is opened, saved, or closed. This only happens on my MacBook, My Desktop Mac Running Catalina Does not have this issue... As of yet. I'm also using the professional license of Fusion 360. The problem started a few months ago but have been using the Pro version for more than a year, so I don't know if this would happen on the non paid version. I updated Node on my laptop to the latest stable version, but that didn't have any effect. 

Node Running 100%

The only solution I have found is to force quit the process every time I open or save a file. 

[bjorn29W5Q]

Same here on an M2 Mac. About 100% CPU used by ~/Library/Application Support/Autodesk/webdeploy/production/29052a16d01271aec3af412bcbb43ce54459adfb/Autodesk Fusion 360.app/Contents/Frameworks/NODEJS/bin/node

Force Quit on the node process solves it until I open or save a project again. I don't see the bad behaviour when just closing a project.

Setup:

Fusion 360 2.0.15050 x86_64 [Rosetta 2]
Active Plan: Personal
macOS 13.1 (22C65) on Mac14,2

[bjorn29W5Q]

@karina.harper did you find a solution for this? I can send debug dumps of the node process or anything else that's helpful. This is 100% reproducible for me.

[bjorn29W5Q]

Looks like I wasn't on the latest version. But upgrading doesn't fix the issue. Now I'm on:

Fusion 360 2.0.15299 x86_64 [Rosetta 2]
Active Plan: Personal
macOS 13.1 (22C65) on Mac14,2

The offending binary is now ~/Library/Application Support/Autodesk/webdeploy/production/6a4ee1e135d539f7735a031beb7a5c1c01c7a76f/Autodesk Fusion 360.app/Contents/Frameworks/NODEJS/bin/node

[bjorn29W5Q]

This is still happening in the latest version:

Fusion 360 2.0.15509 x86_64 [Rosetta 2]
Active Plan: Personal
macOS 13.2.1 (22D68) on Mac14,2

[bjorn29W5Q]

This has now gotten worse. The node process now restarts after Force Quit, so it's constantly eating 100% of one CPU.

Fusion 360 2.0.16009 x86_64 [Rosetta 2]
Active Plan: Personal
macOS 13.3.1 (22E261) on Mac14,2

[ryan.grepper]

I agree it's gotten worse.  I'm on a Macbook Pro running Ventura 13.4 (single user paid license) and now end task is no longer stopping the issue.  I need to turn off wifi, "Force Quit" node and then work offline.  I can turn wifi back on and work for a while, but as soon as I save or open a new file the Node issue is back.