Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determines CPU to boost uncontrolably after update to 2024.1 #2093

Closed
sorinvasilescu opened this issue Apr 18, 2024 · 6 comments
Closed

Determines CPU to boost uncontrolably after update to 2024.1 #2093

sorinvasilescu opened this issue Apr 18, 2024 · 6 comments
Assignees
Labels
type: bug Something isn't working

Comments

@sorinvasilescu
Copy link

Current Behavior

After the latest IntelliJ update (2024.1), each time after launching IntelliJ I get an orphaned process (process remains open after the IDE is closed) that determines the CPU to boost wildly until it ramps up the fans to max and starts overheating (temps in the 90s C).

The process is /usr/local/bin/node /Users/sorin/Library/Application Support/JetBrains/IntelliJIdea2024.1/plugins/nx-console/nxls/main.js --stdio

The process continues to run after the IDE is closed. Several such processes remain if the IDE is closed and reopened several times. The process must be sigkilled, does not respond to sigterm and seems to otherwise keep running indefinitely.

Note: This is not related to any IntelliJ indexing or other processes and completely goes away when disabling the nx-console plugin

Expected Behavior

Don't make my laptop sound like it wants to take off.

Steps to Reproduce

  1. Start IntelliJ with the nx-console plugin enabled
  2. Hear your laptop spin its fans like crazy

Failure Logs / Images / Videos

Environment

  • MacBook Pro 16 2019 with Intel i9, MacOS Sonoma 14.4.1 (23E224)
  • Nx Console version: 1.21.0
  • IntelliJ version: 2024.1
@sorinvasilescu sorinvasilescu added the type: bug Something isn't working label Apr 18, 2024
@MaxKless
Copy link
Collaborator

Thanks for the report @sorinvasilescu this really shouldn't happen!

Could you provide some logs?
Go to Help > Diagnostic Tools > Debug Log Settings... and then insert #dev.nx.console:trace. Then paste the idea.log or sections of it when the error happens.

Also the daemon.log & daemon-error.log would be useful. You can find their location by running nx daemon --log

I suspect something is wrong with file watching, there should be logs in this case. Thank you!

@MaxKless MaxKless self-assigned this Apr 18, 2024
@fjanicki
Copy link

Getting the same thing.

@jaysoo
Copy link
Member

jaysoo commented May 1, 2024

This is related to #2031

@MaxKless
Copy link
Collaborator

MaxKless commented May 3, 2024

Hey! Can you try on the latest version? :) I made some changes that should fix these issues.
If you could report back whether it still happens on 18.21.0/1.23.0 that would be amazing!

@sorinvasilescu
Copy link
Author

Sorry for the lack of answers, apparenlty my Github notifications are going to a black hole 😂

Yeah, about #2031, I wouldn't say high CPU load, I mean I could barely feel it, but what it does happen on these Intel Macs is that certain patterns cause them to boost non-stop, which while not showing up as high CPU load per se, really hurts thermals, acoustics (fan are at 100%) and battery life.

Looks perfectly ok after updating to 1.23.0, after the initial start-up the CPU ramps down and settles at a normal 50 degrees C.
Also, quitting the IDE also closes that node process in a consistent manner.
From my point of view, this can be closed, I can no longer reproduce it.

Great job, thanks a lot for the help and sorry again for the lack of earlier response.

@MaxKless
Copy link
Collaborator

MaxKless commented May 6, 2024

No worries, thanks for the patience!
Closing this as completed. Let me know if anything similar crops up again :)

@MaxKless MaxKless closed this as completed May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants