Pymakr triggers runaway rg searches (100% CPU) on large Python workspace

[samiashi]

Summary
Pymakr appears to trigger repeated workspace searches (ripgrep/rg) that peg CPU at 100% when the workspace has large file churn (e.g., running pytest). Disabling Pymakr immediately stops the spike.

Environment
Pymakr version: 2.22.5
OS: macOS Tahoe (26.2)
VS Code: Stable 1.109.0 (Universal)
Workspace: large Python/Django repo

Steps to reproduce

1. Open a large Python workspace in VS Code.
2. Ensure Pymakr is enabled.
3. Run pytest in a terminal for the workspace.
4. Observe Activity Monitor: many rg processes spawned by Code Helper (Plugin) and CPU pegged at ~100%.
5. Disable Pymakr in the workspace and repeat: CPU spike no longer occurs.

Expected
No runaway ripgrep searches or CPU spike caused by the extension during normal workspace file churn.

Actual
Repeated rg processes and CPU pegged to ~100% until VS Code is closed or Pymakr is disabled.

Notes
Issue was isolated with VS Code Extension Bisect: Pymakr was the culprit.
If you need more details (logs or profiling), let me know and I can capture them.

[Josverl]

The company pycom does not exist any more, and therefore there is no maintenance to pymakr anymore.
You could see if MicroPico may be a relevant option.
It is based off Pymakr , and allows for Pico and other devices.

[samiashi]

I see. Thanks @Josverl

[Josverl]

I have seen this myself while I was using pymakr, and iirc this is caused by filesystem change notifications on folder trees, that VSCode implements using a re subprocess.

It can be partially mitigated by excluding some workspace folders in the VSCode settings. I can't recall which settings exactly though.