-
Notifications
You must be signed in to change notification settings - Fork 53
Description
The extension seems to have strangely high usage of both CPU and memory - even after it's done indexing the workspace and I'm not doing anything other than keeping two SV files open, it's consuming roughly 45-50% of 4 CPU cores (so "200%" total), and jumping between 2.5 and 4 GB of RAM usage.
This seems like a bug, any idea what might cause it?
For context: my workspace is a medium-sized monorepo and the status bar says "SystemVerilog: 61713 indexed objects", so there is a bit to keep track of. However, I'd expect the activity to stabilize once done indexing (until I actually use some of the functionality), and the continued (large) fluctuations in RAM usage seem to indicate that it's doing something over an over which might intuitively not be needed?
EDIT: VSCode version
Version: 1.105.1 (user setup)
Commit: 7d842fb85a0275a4a8e4d7e040d2625abbf7f084
Date: 2025-10-14T22:33:36.618Z
Electron: 37.6.0
ElectronBuildId: 12502201
Chromium: 138.0.7204.251
Node.js: 22.19.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100
Extension version: v0.13.11, running on RHEL 8.10 via SSH remote