Everytime something goes wrong capturing a screenshot (i.e. no response, timeouts, ...) the function exits without closing page and browser, so that chrome instances keep growing until server dies.
Putting page.close() and browser.close() in a "finally" block should avoid resources leaking
Everytime something goes wrong capturing a screenshot (i.e. no response, timeouts, ...) the function exits without closing page and browser, so that chrome instances keep growing until server dies. Putting page.close() and browser.close() in a "finally" block should avoid resources leaking