This commit is contained in:
@@ -25,7 +25,9 @@ ISSUE: reporting failing on linux under load
|
|||||||
maybe a setting for a hard limit on number of reports currently running or instances of chrome started by report
|
maybe a setting for a hard limit on number of reports currently running or instances of chrome started by report
|
||||||
zombie processes?
|
zombie processes?
|
||||||
https://developers.google.com/web/tools/puppeteer/troubleshooting#running_puppeteer_in_docker
|
https://developers.google.com/web/tools/puppeteer/troubleshooting#running_puppeteer_in_docker
|
||||||
|
READ THIS TOO IT'S RELEVANT:
|
||||||
|
https://github.com/dotnet/runtime/issues/21661
|
||||||
|
https://stackoverflow.com/questions/43122080/how-to-use-init-parameter-in-docker-run#44689700
|
||||||
|
|
||||||
todo: rejig render stuck process killer to be thread safe and have a configurable number of allowed running simultaneous headless browser pdf processors
|
todo: rejig render stuck process killer to be thread safe and have a configurable number of allowed running simultaneous headless browser pdf processors
|
||||||
ideally it should allow at least two or three instances at once and track all and return a server busy response to try again if no free slot available
|
ideally it should allow at least two or three instances at once and track all and return a server busy response to try again if no free slot available
|
||||||
|
|||||||
Reference in New Issue
Block a user