check failed: stack_overflow()
See original GitHub issueThis is the error
#
# Fatal error in , line 0
# Check failed: stack_overflow().
#
#
#
#FailureMessage Object: 0x7ffdc48c3860
1: 0xb6d391 [FaxSto]
2: 0x1bf6a04 V8_Fatal(char const*, ...) [FaxSto]
3: 0x113ae31 v8::internal::Parser::DoParseFunction(v8::internal::Isolate*, v8::internal::ParseInfo*, int, int, int, v8::internal::AstRawString const*) [FaxSto]
4: 0x113b2dc v8::internal::Parser::ParseFunction(v8::internal::Isolate*, v8::internal::ParseInfo*, v8::internal::Handle<v8::internal::SharedFunctionInfo>) [FaxSto]
5: 0x1144104 v8::internal::parsing::ParseFunction(v8::internal::ParseInfo*, v8::internal::Handle<v8::internal::SharedFunctionInfo>, v8::internal::Isolate*, v8::internal::parsing::ReportStatisticsMode) [FaxSto]
6: 0x11444fd v8::internal::parsing::ParseAny(v8::internal::ParseInfo*, v8::internal::Handle<v8::internal::SharedFunctionInfo>, v8::internal::Isolate*, v8::internal::parsing::ReportStatisticsMode) [FaxSto]
7: 0xe421e4 v8::internal::ErrorUtils::ThrowLoadFromNullOrUndefined(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::MaybeHandle<v8::internal::Object>) [FaxSto]
8: 0x11fa7ef v8::internal::Runtime::GetObjectProperty(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, bool*) [FaxSto]
9: 0x11fd98f v8::internal::Runtime_GetProperty(int, unsigned long*, v8::internal::Isolate*) [FaxSto]
10: 0x15e7cf9 [FaxSto]
Trace/breakpoint trap (core dumped)
I’ve read the readme and it mentions arrow functions to be a possible cause. However, only some users using my application experience this issue whereas others are completely fine.
So this made me think if it’s a compiling issue or if it’s another possible issue.
Their OS (Ubuntu 20.04 LTS) and node version (16.13.2) are the same as others who are also using the application.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9
Top Results From Across the Web
ec2 Instance Status Check Failed - Stack Overflow
An instance status check failure indicates a problem with the instance, such as: Failure to boot the operating system; Failure to mount ...
Read more >Debugging a Stack Overflow - Windows drivers | Microsoft Learn
A stack overflow is an error that user-mode threads can encounter. There are three possible causes for this error:.
Read more >What is a stack overflow error? - TechTarget
A stack overflow is a type of buffer overflow error that occurs when a computer program tries to use more memory space in...
Read more >Stack Overflow CAPTCHA-Check fails - Oops! Robot detection ...
I try to post an answer to a question in Stack Overflow, than get CAPTCHA-Check with the box to click. After clicking I...
Read more >1235182 - V8 DCHECK stack position > stack guard in Isolate
Hello, I found this bug (DCHECK) via fuzzing. ... # Debug check failed: GetCurrentStackPosition() >= stack_guard()->real_climit() - 8 * KB (140729015611600 vs.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Removing the arrow functions from that query that failed above fixed it.
Try and see if it solve your problem. The error is not specific to one cause, so we don’t know unless we know your exact code.
Arrow functions cause that sort if error, so removing them might help you.