Wappalyzer: High number of cpu hungry "rogue" chromium instances

[AdityaAnand1]

I'm getting the sense that I'm pushing this library to it's limits, concurrently having multiple processes set up, churning through thousands of URLs:

This is on windows, AFTER killing ~5 processes iterating through URLs with wappalyzer

Whenever I try to do this, my computer (high end workstation) ends up grinding to a halt and I have to slowly force kill processes and even when the node processes are dead, the chromium processes stick around and for some reason they demand a ton of CPU usage.

I'm guessing for a similar reason, I haven't been able to use this in virtual machine/servers as well, it ends up eating too much memory/CPU - so much so that I have no other choice to kill the processes.

Any ideas how to solve this?

[AliasIO]

I'm not sure why the processes stick around. You could perhaps try using Docker and stop the container when the process is done.

[AdityaAnand1]

That doesn't really solve the problem, the container's memory will fill up and the container will just stop responding.

[AliasIO]

I'm currently working on a Puppeteer-only driver that will let you run multiple scans with a single browser instance, stay tuned.

[AliasIO]

Please see:

https://github.com/AliasIO/wappalyzer/issues/3081#issuecomment-633806251