From fd443f0e3e3bf839450f00d3c629f30dbdc6e45d Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Mon, 27 Dec 2021 15:22:08 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index f9d80c6b..5d16a16b 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -259,6 +259,7 @@ TODO: 1 BETA DOCS: the moment it has to swap it pretty much stands still So now, with the current settings for chromium the timeout can once again take hold on a 1gb droplet setting it to 1m max render time seems to catch all the out of memory swap conditions + UPDATE: probably the no-shm command line parameter causing it to run out of ram with no swap happening to crash it todo: figure out the appropriate timeout and range that a 2gb droplet can handle (and maybe larger ones as well for completeness) testing with service wo's dispatch report