Scanning stuck on possible memory leak

[fhafner2]

I enabled this on many projects that I take care of, but one of them is currently stalled:

$ cd /tmp/detector && npm ci
(node:143) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 socket listeners added to [ClientRequest]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)

Anyone had similar issues?

[gensecai-dev]

Hi,

Thanks for writing in . Can you please help us with following info to check it further :

Try clearing npm cache: npm cache clean --force

• is this project-specific or affects all of your projects ?
• Try npm ci --maxsockets=5 to limit concurrent connections

Best

[fhafner2]

setting --maxsocket=5 did the trick here. Thanks!