RangeError Maximum call stack size exceeded in cloneCallSite
See original GitHub issueWe are experiencing a RangeError similar to issue #93 in our Node.js app. I haven’t been able to reproduce it and it seems to be occurring randomly at times.
/usr/src/app/node_modules/source-map-support/source-map-support.js:331
Object.getOwnPropertyNames(Object.getPrototypeOf(frame)).forEach(function(name) {
^
RangeError: Maximum call stack size exceeded
We are using the latest version 0.5.13 and latest 10 version of Node.js
Issue Analytics
- State:
- Created 4 years ago
- Reactions:7
- Comments:6
Top Results From Across the Web
JavaScript RangeError: Maximum Call Stack Size Exceeded
The RangeError: Maximum call stack size exceeded is thrown when a function call is made that exceeds the call stack size. This can...
Read more >javascript - Maximum call stack size exceeded error
It means that somewhere in your code, you are calling a function which in turn calls another function and so forth, until you...
Read more >JavaScript Error: Maximum Call Stack Size Exceeded
A RangeError typically means an error has occurred outside of a code's argument value for its parameter. Now that you know a little...
Read more >RangeError: Maximum call stack size exceeded - Educative.io
RangeError : Maximum call stack size exceeded ... not being met and is, therefore, calling the function again and again until you hit...
Read more >How to fix: "RangeError: Maximum call stack size exceeded"
A "RangeError: Maximum call stack size exceeded" is an error that occurs when a function or operation tries to execute too many nested...
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
I’ve been having the exact same problem when debugging a TypeScript mocha test. I am using RubyMine, and this is the command line that starts the debug session:
A few seconds later, mocha exits and I can see the following stack trace:
The source-map-support version I have in my project is
0.5.19
.I experienced the same issue. I used webpack v5 with typescript. The fix for me was changing
devtool: 'inline-source-map',
to
devtool: 'source-map',
in my webpack.config.js