Marcel Laverdet

What is the exit code of the process? If it's 0 this is often caused by an abandoned promise if you're using a memoryLimit of

I tried to start your service via Docker by running the command included in the readme: `docker-compose up transformer-no-func`. It looks like python is missing in your image I received...

In my personal experience, and this varies by nodejs version, limits under 128mb tend to be unreliable. v8 is super thirsty for memory.

When you set `context->AllowCodeGenerationFromStrings(false)` it ends up invoking the callback from `isolate->SetModifyCodeGenerationFromStringsCallback(...)` which we use to prevent invoking the parser with huge strings. Otherwise it was super easy to crash...

Can you post your complete case instead of a snippet?

If you had an example of this issue which doesn't depend on kubernetes or docker that would be helpful.

Thanks, this is an interesting case. It's resolved in the v8-heap branch. I still have a few more issues I need to resolve and then I'll roll the fix into...

On node v12.0.0+ the iterator case is halted correctly, without crashing the main process. It does still crash on node v10.x, though. I did some digging and the behavior changed...

Thanks for the new report. I bisected this issue back to v8 commit v8/v8@17dd105144044469a0c24ca7ef9f53225b9b8345, and it seems that v8 is still broken today. I will have to forward this to...

2.0.0 is on npm with the fix for the spread operator. I opened a v8 issue for the `Array..fill` crash here [Issue 9368: Array..join is uninterruptible](https://bugs.chromium.org/p/v8/issues/detail?id=9368). Until I hear back...