Sam Cao

Did you try JavetShell? It's an APK. You just install it and run it. It's a GUI that does what you describe.

That's something I cannot help with.

That's how Node.js works. It needs the working directory to be the one. In your case, you may do whatever you want to do with the working directory afterwards.

Thank you for reporting this issue. It is not recommended to do that in Javet because there is no **sparse array** in Java so that Javet directly maps JS array...

By the way, I tried that in Node.js. Node.js crashes as well. It doesn't even have enough time printing the whole call stack before being killed. 

> I will try to avoid using such syntax, but since our platform is user-facing, we cannot perfectly control user input, so we need to address this issue. Agree. Anything...

I spent a few hours analyzing the source code of Node.js and V8. Unfortunately, `OS.Abort()` is hardcoded in V8 after OOM. If you try the same in Chrome console, that...

> I collect all the created V8 engines, and check them with a timer task every 100ms. If their memory usage exceeds the threshold I've set, I use the 'terminateExecution'...

> I think this is a good idea. Currently, JavetEngineGuard can only limit the execution time of the engine. More resource limitations could be added, such as memory, CPU usage,...

Yesterday I published [Break Serverless in Node.js Easily](https://sjtucaocao.medium.com/break-serverless-in-node-js-easily-c73b8c9ca13) in which I mentioned: > The higher frequency it profiles with, the more CPU cycles does it require, the less crash will...