website-screenshot

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

Jan	FEB	Mar
	02
2021	2022	2023

website-screenshot

Here are 20 public repositories matching this topic...

sindresorhus / capture-website

page.close() and browser.close() should be in try-catch-finally block

sindresorhus / capture-website-cli

deadcoder0904 / awesome-website-screenshots

ScullWM / chart-to-aws

saadmk11 / comment-webpage-screenshot

urlbox / urlbox-screenshots-node

MrBotDeveloper / API

urlbox-io / urlbox-screenshots-php

screenshotmachine / screenshotmachine-python

screenshotmachine / screenshotmachine-php

screenshotmachine / screenshotmachine-vb

website-template / bootstrap-2-ismailtasdelen.com

screenshotmachine / screenshotmachine-java

screenshotmachine / screenshotmachine-nodejs

Pabex / websitescreenshot

screenshotmachine / screenshotmachine-bash

screenshotmachine / screenshotmachine-csharp

whois-api-llc / screenshot-py

screenshotmachine / screenshotmachine-perl

gdhebling / photographer-portfolio

Improve this page

Add this topic to your repo