You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
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 thev
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.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)
The text was updated successfully, but these errors were encountered: