From 27910abad9ec4e50bf6bc59c26e4f065d23a616a Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Thu, 28 Oct 2021 00:14:28 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index b73b2a12..8896de08 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -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 zombie processes? 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 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