174 chrome instances running on firecrawl droplet
Hi, I just observed the usage of the self deployment of firecrawl. I'm using the docker compose to deploy firecrawl on a DO droplet.
I saw 100% CPU usage and I was very suspicious. I ssh'ed into the droplet and found that 174 chrome instances are running, it almost seems like it doesn't clean up the chrome instances properly.
Is anyone having similar issue or is this a somewhat of a known issue?
4 Replies
I guess the question is, how many chrome processes should I expect to see when I run
top command on the droplet running firecrawl?Here's the graph of the usage, I turned the droplet off when it was 100% and immediately restarted the service, you can see the gradual growth of the chrome instances
I grabbed the running logs up to the point of 100% CPU usage. Is there anyone that can help me debug this?
Hey Purnama! Apologies for the delay in answering.
We're in the process of optimizing our CPU load on firecrawl. CCing @Adobe.Flash for more