The short answer is: I don't know and those are valid concerns. The first issue you bring up is really one about resource limiting. You would want a mechanism

The short answer is: I don't know and those are valid concerns. The first issue you bring up is really one about resource limiting. You would want a mechanism to set resource limits (CPU, memory, execution time etc) and then be able to pause/unpause, throttle, terminate, restart or perform some other action when you hit a resource limit. It is safe to assume people will make mistakes. :-) It has been a while since I looked at runtimes, but I don't think resource limits would necessarily be that hard to implement. It seems to me that preventing crashing the surrounding program isn't something you can necessarily address in a runtime. Any library or component you use in your Go code can potentially crash the program. And if you project APIs into the sandbox that can be called in ways that crash the surrounding program, that's mostly on you, the programmer, and not really something I think the runtime could reasonably prevent.