SimDdong
SimDdong
> 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...
I think this error has something to do with chromium. i gave up
@Bonauze I think it is related to Chromium.. But I don't know what the exact cause is. Now memory is increasing little by little, so it can be ignored... But...
I think the cause of memory leak is chromium. so my solution is I restart docker container every day.
@marconi1992 yes. that's right. Can I catch routing events from other spas?