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

redhat.ansible-2.9.118/out/server/src/server.js --node-ipc does not terminate when code is closed and high CPU usage #1152

Open
piengeng opened this issue Dec 7, 2023 · 2 comments
Assignees
Labels
bug Something isn't working new

Comments

@piengeng
Copy link

piengeng commented Dec 7, 2023

Summary

infinite loop behaviour on this extension when spinning up node server.js , that later results in high CPU usage.

Extension version

2.9.118

VS Code version

1.84.2

Ansible Version

ansible [core 2.15.7]
  config file = ~/.ansible.cfg
  configured module search path = ['~/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3/dist-packages/ansible
  ansible collection location = ~/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/bin/ansible
  python version = 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (/usr/bin/python3)
  jinja version = 3.0.3
  libyaml = True

OS / Environment

Ubuntu 22.04.3 LTS ansible-lint 6.22.1

Relevant log output

No response

@piengeng piengeng added bug Something isn't working new labels Dec 7, 2023
@ssbarnea ssbarnea transferred this issue from ansible/vscode-ansible Jan 3, 2024
@ssbarnea ssbarnea transferred this issue from ansible/ansible-language-server Mar 15, 2024
@bendem
Copy link

bendem commented Apr 3, 2024

Been having that problem for a long time. So often that when my fan starts spinning, I just run pkill -f 'redhat.ansible-.*/out/server' before checking what's wrong.

@piengeng
Copy link
Author

piengeng commented Apr 3, 2024

yeah, been using kill to workaround and sometimes have to restart vscode just to continue the ansible script, kinda relying on linter to filter mistakes/errors.

Rather annoying to kill it everytime, makes ppl wonder why such CPU usage, a bit like the "ssh xz code injection/hack CVE-2024-3094" recently, but i'm just not that capable to pinpoint the exact cause. lol. Who knows maybe someone investigate turns out it's another kind of injection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working new
Projects
Status: Roadmap
Development

No branches or pull requests

3 participants