Maximum call stack size error when press 'delete' button in empty mathfield
See original GitHub issueDescribe the bug When press ‘Delete’ button in empty mathfield, maximum call stack size error occurs.
To Reproduce
- Go https://mathlive.io/
- See any examples and clear mathfield using ‘Backspace’ or ‘delete’ button
- Press ‘delete’ button
- Here comes
range error: maximum call stack size exceeded.
!
Expected behavior With no errors, nothing happens.
Screenshots
Environment
- Device: PC
- OS: [Windows 10]
- Browser [Chrome]
- Version [0.33]
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 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 Error: Maximum Call Stack Size Exceeded
When recursive code is missing its base code or shoots past the base code, it will repeatedly keep calling itself until you hit...
Read more >JavaScript RangeError: Maximum Call Stack Size Exceeded
The JavaScript RangeError: Maximum call stack size exceeded is an error that occurs when there are too many function calls, or if a...
Read more >I can't open Eagle, it prompted message "Maximum call stack ...
Click the Win button in the lower-left corner, search for %appdata%. Delete the "Eagle" folder. Restart Eagle to see if the problem is...
Read more >Maximum call stack size exceeded - EJ 2 Forums - Syncfusion
Forum Thread - Maximum call stack size exceeded - When Trying to Empty ComboBox DataSource - ASP.NET Core - EJ 2.
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
Hmmm… Not exactly sure what happened, but it should be fixed now in 0.33.2
OK, got it. It’s not related to deleting, as the original bug report indicate, but it’s an infinite loop that happens under different circumstances. Thanks for the additional info and for the fix. I’ve opened #394 to track the issue. I’d be happy to take a PR, otherwise I’ll merge in your changes manually. Either way, thank you.