https://bellard.org/quickjs/quickjs.html#Memory-handling
It looks like quickJS can let memory limits, that would be useful if you wanted to let users upload their own functions but limit the amount of allowed memory. Being able to get the current memory usage, such as profiling too. I see there is a way to dump memory usage in QuickJS. If so, then someone could use that and the termination hooks to write their own logic to enforce memory usage.
Also be useful if the Execution timeout and interrupts timeouts was there. Could see this maybe being useful for things you might use V8 Isolates for, but not sure if this would be lighter weight on the memory side.
Very interesting project though, could see this being useful on both the server side and client side too. Say if you were making a virtual world or a game engine, could let people run sandbox limited server scripts or even local scripts on the client side.
https://bellard.org/quickjs/quickjs.html#Memory-handling
It looks like quickJS can let memory limits, that would be useful if you wanted to let users upload their own functions but limit the amount of allowed memory. Being able to get the current memory usage, such as profiling too. I see there is a way to dump memory usage in QuickJS. If so, then someone could use that and the termination hooks to write their own logic to enforce memory usage.
Also be useful if the Execution timeout and interrupts timeouts was there. Could see this maybe being useful for things you might use V8 Isolates for, but not sure if this would be lighter weight on the memory side.
Very interesting project though, could see this being useful on both the server side and client side too. Say if you were making a virtual world or a game engine, could let people run sandbox limited server scripts or even local scripts on the client side.