Random call stack size exceeded in binaries complied with node v12.2.0
See original GitHub issueThanks for updating pkg to support node v12!
It seems that there is a weird bug causing random Maximum call stack size exceeded errors ONLY in binaries complied by pkg targeting node v12.2.0:
Binary compiled by pkg |
Run directly through node |
|
---|---|---|
node v10.15.3 | ✅ | ✅ |
node v12.2.0 | Maximum call stack size exceeded |
✅ |
(Tested on Linux / CentOS 7)
Unfortunately, the original code is part of a proprietary software so I could not post it here. But since it does not deal with files, I’m pretty sure the issue is not related to the snapshot file system.
Here are some stack trace samples, seems fully random, the only thing in common is the RangeError: Maximum call stack size exceeded
:
06:25:30 [22016]: events.js:196
06:25:30 [22016]: Reflect.apply(handler, this, args);
06:25:30 [22016]: ^
06:25:30 [22016]: RangeError: Maximum call stack size exceeded
06:25:30 [22016]: at Object.emit (events.js:196:13)
06:25:30 [22016]: at endReadableNT (_stream_readable.js:1130:12)
06:25:30 [22016]: at processTicksAndRejections (internal/process/task_queues.js:84:9)
06:07:11 [11185]: _stream_transform.js:140
06:07:11 [11185]: this._flush((er, data) => {
06:07:11 [11185]: ^
06:07:11 [11185]: RangeError: Maximum call stack size exceeded
06:07:11 [11185]: at String.replace (<anonymous>)
06:07:11 [11185]: at Object.prefinish (_stream_transform.js:140:10)
06:07:11 [11185]: at Object.emit (events.js:196:13)
06:18:41 [18060]: internal/timers.js:531
06:18:41 [18060]: timer._onTimeout();
06:18:41 [18060]: ^
06:18:41 [18060]: RangeError: Maximum call stack size exceeded
06:18:41 [18060]: at listOnTimeout (internal/timers.js:531:17)
06:18:41 [18060]: at processTimers (internal/timers.js:475:7)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:42
- Comments:72 (4 by maintainers)
Top Results From Across the Web
Random call stack size exceeded in binaries complied with ...
Thanks for updating pkg to support node v12! It seems that there is a weird bug causing random Maximum call stack size exceeded...
Read more >Maximum call stack size exceeded on npm install
from the official docs: > This command runs the npm build command on the matched folders. This is useful when you install a...
Read more >Node.js v19.3.0 Documentation
Added in: v14.2.0, v12.19.0. Iterates through the list of functions passed to tracker.calls() and will throw an error for functions that have not...
Read more >Random crashes with "Maximum call stack size exceeded"
Go to the node-red folder and try the command npm ls graceful-fs This should show you a dependency tree. When you find out...
Read more >Changelog - Cypress Documentation
ngOnChanges is now called after mounting an Angular component in component testing. Fixes #23591. Code frames for Vite project stack traces now point...
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
Fixed in 4.4.1. Please try
Same error occurs on Linux / Ubuntu.
Indeed it seems to be VERY random. Here are some of my stack traces:
Besides: You do a great job with
pkg
!