Shirshak

whats the point of doing `await page.setCacheEnabled(true);` when it is enabled by default? Regarding leak it may be due to upstream like i tried to open 200 tabs and closed...

@sdg9670 can u try with playwright if it produces mem leaks there also. Yes this is serious issue because it means we cannot leave browser handle running for long period...

Guys this is not puppeteer issues its a chrome issue.

@juniorb2ss 64gb ram so no problem in ram. And i have set to 20gb in php.ini files. Hmm no i designed it for windows so i cannot install dockers etc...

just use like open 100 command prompt and run the app. 1 start the app 2 start the app 3 start the app 4 start the app 5 start the...

no api has no limit because i use proxy. When i open same api from browser it shows. 100 is definitely coming from somewhere because this problem starts at 100...

can u say me related to process number? and how do i know if cores are limiting it?

This is not a duplicate of 1661 if you look at the error closely. Closing this

@niieani the project doesn't seem to be active and it's already been more than 4 months so I don't want to pressure the maintainer.

I am not frustrated but delighted to hear the project is active. When I saw there are workarounds I closed them. As it is open-source it doesn't impact me if...