Subj : src/sbbs3/jsexec.c
To   : Git commit to main/sbbs/master
From : Rob Swindell (on Windows 11)
Date : Fri Dec 08 2023 17:37:09

https://gitlab.synchro.net/main/sbbs/-/commit/7b932f63e4f1d4275e55dfbf
Modified Files:
	src/sbbs3/jsexec.c
Log Message:
Only create/use a single run-time for use in JSexec, even when re-runnning

The '-l' (loop) option would cause the JS runtime to be destroyed and
recreated for each new execution of the script, which resulted in memory
leaks in Windows builds (see issue #672 for details). So instead, just
use a single JS runtime here when the -l option is used to prevent that
from happening, though truth be told, that's likely not a normal/common
occurrence. Other apparent JS-related memory leaks (e.g. in the web
server) appear to be of a common concern.

Likely upgrading to a modern libmozjs would also fix this issue, but
we're far short of being able to do that right now.
--- SBBSecho 3.20-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.