Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Maximum call stack size exceeded error after upgrading to 0.20.4
See original GitHub issueUsing the following chart:
<ResponsiveContainer width="100%" height="100%">
<RadialBarChart cx="50%" cy="100%" innerRadius="1%" outerRadius="100%" data={data} onClick={::this.requestTagsWithPattern} >
<Legend align="left" verticalAlign="top" onClick={::this.requestTagsWithPattern} />
<RadialBar label={radialLabelStyle} className="clickable" minAngle={15} background clockWise={true} dataKey="uv" />
<Tooltip />
</RadialBarChart>
</ResponsiveContainer>
I am receiving the following error when hovering over the RadialBar:
util.js:51 Uncaught RangeError: Maximum call stack size exceeded[Symbol.replace]
@ (program):665replace
@ (program):119generatePrefixStyle
@ util.js:51(anonymous function)
@ util.js:119reduce
@ (program):999translateStyle
@ util.js:118render
@ Tooltip.js:220(anonymous function)
@ ReactCompositeComponent.js:796measureLifeCyclePerf
@ ReactCompositeComponent.js:75_renderValidatedComponentWithoutOwnerOrContext
@ ReactCompositeComponent.js:795
This issue started occurring after upgrading from 0.20.2 to 0.20.4.
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
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 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 Error: Maximum Call Stack Size Exceeded
More specifically, the issue lies with the function calling on itself indefinitely.
Read more >Debug node causing RangeError: Maximum call stack size ...
The error happens 6 seconds before the gpsd entry (14:31:55 the "RangeError: Maximum call stack size exceeded" and 14:32:01 the gpsd entry).
Read more >Changelog - Cypress Documentation
Installing Cypress on your system now requires Node.js 14, 16 or 18+. ... The error Maximum call stack size exceeded will no longer...
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 recharts@0.20.5.
@xile611 After updating to 0.20.5, I am no longer encountering the issue. Thanks for the quick turnaround on this.