Image border causes "Maximum update depth exceeded" error
See original GitHub issue- Go to https://codesandbox.io/s/wild-sun-bvg77?file=/src/App.js
- Click “Set bad crop data” in rendered view
- Error: Maximum update depth exceeded should be thrown
version 8.6.2
Possibly related to this https://github.com/DominicTobias/react-image-crop/issues/347 but in this scenerio, it only happens when a border is set on the image. (See styles.css
)
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
React question: Error: Maximum update depth exceeded
Error: Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or ...
Read more >Fix the "Maximum Update Depth Exceeded" Error in React
Here I'll discuss the most frequent causes and how to fix them. Cause 1: Calling a Function Rather Than Passing a Reference to...
Read more >D] Maximum update depth exceeded. Not sure how to resolve ...
Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate.
Read more >[Solved]-React : Maximum update depth exceeded-Reactjs
Coding example for the question React : Maximum update depth exceeded-Reactjs.
Read more >'Maximum update depth exceeded' error with Sortable #496
Here is an example: https://codesandbox.io/s/dnd-kit-issue-eq952 Screen.Recording.2021-10-29.at.11.54.08.mov The problem is because of items ...
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 FreeTop 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
Top GitHub Comments
Damn I know what’s wrong, will fix in next release and deprecate 8.6.3
Fixed in 8.6.3