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