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

v-analyzer randomly stopping and then restarting on top of the old v-analyzer instance #142

Open
xTheFreeZe opened this issue Nov 21, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@xTheFreeZe
Copy link

Describe the bug

It appears that v-analyzer randomly stops working for me.
I was writing some code and the analyzer did an amazing job. It then just stopped giving any erros. I proceeded to restart the server but noticed my computer was using more CPU then it usually does.

After checking all running processes I saw that I had like 4-6 instances of v-analyzer running. These probably came from me restarting the server multiple times. Closing VS Code did not stop these instances. I had to manually stop each v-analyzer process.

On top of that, I had about 40 active v processes running and closing each v-analyzer instance also stopped the v instances from running.

Expected Behavior

v-analyzer analyzing my V code

Current Behavior

v-analyzer stops randomly and when restarting the server, it spaws on top of the old v-analyzer process. Also spawns multiple v processes.

Bildschirmfoto vom 2024-11-21 17-35-02

Bildschirmfoto vom 2024-11-21 17-35-14

Reproduction Steps

When v-analyzer randomly stops working, restart the server.

Possible Solution

No response

Additional Information/Context

No response

Environment details (v doctor output)

V full version: V 0.4.8 da3112e.58fc4de
OS: linux, "Fedora Linux 41 (Workstation Edition)"
Processor: 12 cpus, 64bit, little endian, AMD Ryzen 5 2600 Six-Core Processor

getwd: /home/marwin
vexe: /home/marwin/v/v
vexe mtime: 2024-11-21 14:30:54

vroot: OK, value: /home/marwin/v
VMODULES: OK, value: /home/marwin/.vmodules
VTMP: OK, value: /tmp/v_1000

Git version: git version 2.47.0
Git vroot status: weekly.2024.24-968-g58fc4dea
.git/config present: true

CC version: cc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
emcc version: N/A
thirdparty/tcc status: thirdparty-linux-amd64 0134e9b9

Editor name

Visual Studio Code

v-analyzer Version

0.0.5.ef4243a

VS Code Extension Version

0.0.2 (The v-analyzer extension)

@xTheFreeZe xTheFreeZe added the bug Something isn't working label Nov 21, 2024
@spytheman
Copy link
Member

Can you provide a sample of your code?

If it is a public repository, can you share the link, and describe what part of it you were editing?

@xTheFreeZe
Copy link
Author

xTheFreeZe commented Nov 22, 2024

Sorry for the late response.
It is in this repo: https://github.com/Radon-Language-Team/Radon/tree/new_radon
Specifically, this file: https://github.com/Radon-Language-Team/Radon/blob/new_radon/src/radon/parser/parse_proc_call.v

This bug happened in multiple files by the way. All in this project.

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

No branches or pull requests

2 participants