: High memory usage and CLI incompatibility of Codacy extension on Windows (Cursor/VS Code) #155
Description
Type: Bug
When using the Codacy extension in Cursor/VS Code on Windows, I encountered repeated errors and excessive memory usage caused by the extension’s background processes. The extension continuously tried to launch the Codacy CLI, which is not supported on Windows without WSL.
The error shown in the logs was:
CLI on Windows is not supported without WSL.
Additionally, multiple Node.js processes (codacy-mcp-server, npm -A ^@codacy/codacy-mcp@latest, etc.) were spawned, consuming significant amounts of RAM. In the Cursor Process Explorer, these processes appeared with memory usage ranging from 11 MB up to 71 MB each, stacking up in parallel and increasing overall resource consumption.
Extension version: 1.11.2
VS Code version: Cursor 1.7.29 (5de1e0201c451e9b2865f731faa1e2d4bd875e20, 2025-10-02T03:40:46.214Z)
OS version: Windows_NT x64 10.0.22631
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | AMD Ryzen 3 3200G with Radeon Vega Graphics (4 x 3593) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | undefined |
| Memory (System) | 15.19GB (1.08GB free) |
| Process Argv | |
| Screen Reader | no |
| VM | 0% |