Bug: Timeout control invalidation

[liuzibo]

When using GuardDog for batch detection of malicious packages, I found that GuardDog freezes when detecting large-sized malicious packages.
Therefore, I tried modifying the SEMGREP_TIMEOUT in the analyzer.py file to change the timeout period, but this did not work. As a result, I had to force stop the detection by modifying the timeout parameter in subprocess.run(), yet this causes semgrep-core to keep residing in the process. During large-scale batch detection, this leads to memory exhaustion.

Currently, I can only resolve this issue by forcefully terminating the semgrep-core process every time a timeout occurs. Is there any solution to this problem?

[sobregosodd]

Hello @liuzibo , thanks for reporting this, we'll try to prioritise this

[kulukami]

Is this happening in a Docker or a container?

like this one ? semgrep/semgrep#11251