Open JalonSolov opened 3 weeks ago
Yes, this problem will likely occur on large V files, too, I just have trouble believing anyone will put that much V code in a .v
file. However, it is definitely something that also needs to be addressed.
It also fails on large V projects, such as V itself. When I opened vlib/x/json2/decoder2/decode.v
, v-analyzer crashed with a segmentation fault.
Describe the bug
v-analyzer is not limiting itself to V files.
Expected Behavior
v-analyzer only indexes V related files.
Current Behavior
v-analyzer apparently tries to index ALL files in a project.
In one project, I generated a 13 GB
.txt
file, and v-analyzer started crashing with a segmentation fault. After I deleted that file, v-analyzer worked again.Reproduction Steps
Have a huge file in a V project. Watch it bomb out with a segmentation fault.
Possible Solution
Limit to indexing .v, .vv, and .vsh files. It's fine if it notes the other files' existence, but it should not try to index them.
Additional Information/Context
No response
Environment details (
v doctor
output)Editor name
vscode
v-analyzer Version
v-analyzer version 0.0.4-beta.1.e91f8a4
VS Code Extension Version
v0.0.4