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
Whenever a struct / enum / function definition changes, v-analyzer consumes extra 1-10Mb of RAM that doesn't get freed afterwards, causing it to snowball in long running sessions
Expected Behavior
RAM consumption should remain roughly the same
Current Behavior
RAM consumption slowly goes up the more code gets changed
Reproduction Steps
Open any project
Change any definition several times
Possible Solution
No response
Additional Information/Context
No response
Environment details (v doctor output)
V full version: V 0.4.8 469b56e.7cdd667
OS: linux, "Manjaro Linux"
Processor: 4 cpus, 64bit, little endian, Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz
Describe the bug
Whenever a struct / enum / function definition changes, v-analyzer consumes extra 1-10Mb of RAM that doesn't get freed afterwards, causing it to snowball in long running sessions
Expected Behavior
RAM consumption should remain roughly the same
Current Behavior
RAM consumption slowly goes up the more code gets changed
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
Environment details (
v doctor
output)V full version: V 0.4.8 469b56e.7cdd667
OS: linux, "Manjaro Linux"
Processor: 4 cpus, 64bit, little endian, Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz
getwd: /home/username/Documents/coding/sample_project
vexe: /home/username/Documents/v/v
vexe mtime: 2024-10-10 17:31:34
vroot: OK, value: /home/username/Documents/v
VMODULES: OK, value: /home/usernamei/.vmodules
VTMP: OK, value: /tmp/v_1000
Git version: git version 2.46.0
Git vroot status: weekly.2024.41-4-g7cdd6677
.git/config present: true
CC version: cc (GCC) 14.2.1 20240805
thirdparty/tcc status: thirdparty-linux-amd64 0134e9b9
Editor name
kakoune, zed
v-analyzer Version
v-analyzer version 0.0.4-beta.1.bc5b3ca
VS Code Extension Version
No response
The text was updated successfully, but these errors were encountered: