nodejs
v8::internal::TranslatedState::CreateNextTranslatedValue(int, v8::internal::TranslationArrayIterator*, v8::internal::DeoptimizationLiteralArray, unsigned long, v8::internal::RegisterValues*, _IO_FILE*) [/var/lang/bin/node]
Version
18
Platform
aws lambda
Subsystem
lambda
What steps will reproduce the bug?
Step function state triggering in a loop with 30 records in a batch to be processed.
How often does it reproduce? Is there a required condition?
Frequently since yesterday
What is the expected behavior? Why is that the expected behavior?
Step function steps executino should be finished for all batches, instead processing only few steps and randomly failing.
What do you see instead?
Fatal error in , line 0
Check failed: !maybe.IsCleared().
#FailureMessage Object: 0x7ffd5bd188 1: 0x5560804320 [/var/lang/bin/node] 2: 0x55619bc788 V8_Fatal(char const*, ...) [/var/lang/bin/node] 3: 0x5560b0eb38 v8::internal::TranslatedState::CreateNextTranslatedValue(int, v8::internal::TranslationArrayIterator*, v8::internal::DeoptimizationLiteralArray, unsigned long, v8::internal::RegisterValues*, _IO_FILE*) [/var/lang/bin/node]
4: 0x5560b12208 v8::internal::TranslatedState::Init(v8::internal::Isolate*, unsigned long, unsigned long, v8::internal::TranslationArrayIterator*, v8::internal::DeoptimizationLiteralArray, v8::internal::RegisterValues*, _IO_FILE*, int, int) [/var/lang/bin/node]
5: 0x5560b081c0 v8::internal::Deoptimizer::DoComputeOutputFrames() [/var/lang/bin/node] 6: 0x55614780d4 [/var/lang/bin/node]
Additional information
No response
Hi! Thanks for the issue, but without more context, it's hard to see what exactly went wrong. Could you provide a minimal reproducible example?
A step function has 3 states, where first state collects no. of records to be processed, second state collects a data related to each record and third step state triggers for each batch in a sequence to process the record. The third state of the step function is processing around 8 batches * 10 records successfully but randomly failing with the error posted in the ticket.
Sorry for late response.
Could you provide some reproducible code? We want to see exactly what happened before the error.
Actually, it is not consistent of failing at certain line of code. in our code we are almost interacting with dynamodb around 80 calls, reading compressed file and uncompressing and writing a compressed file form/to s3 multiple times. This is a large function code, failing intermittently with this error at random line of code. Very first time when we run with fresh deployment, it runs well without any error.
If you can give us thoughts what could be potential code issue causing this error so that we can check whether our code has such lines.
Note: we are using lamda runtime as Node.js 18.x and lambda architecture as ARM64 and also tried with x86.
lamda runtime as Node.js 18.x and lambda architecture as ARM64 running on V8 engine
this is exact error that is reported here https://github.com/nodejs/node/blob/v20.x/deps/v8/tools/testrunner/testproc/stack_utils/testdata/analyze_crash/maybe_is_cleared.txt#L12
@RedYetiDev Can you please help on this issue how can we get rid of this error in production env?
I'd love to help, but I think you'll be better assisted by a member of the v8 or core team.
Hi! If you able to reproduce this issue, please do the following:
Open a new issue with a detailed reproduction, including example code and errors. The more detailed the issue, the easier it is to help.
Remember that, in your new issue, make use of markdown features such as code blocks. These features make reading the issues easier and simpler.