Maximum call stack size exceeded in logger
See original GitHub issueDescribe the bug I get this error only in version 3.15.1
Uncaught RangeError: Maximum call stack size exceeded
at Object.warn (logger.js:23)
when the user is signed in
Steps to reproduce Just login
Expected behavior Should load the page
Screenshots or error logs
Uncaught RangeError: Maximum call stack size exceeded
at Object.warn (logger.js:23)
Feedback Documentation refers to searching through online documentation, code comments and issue history. The example project refers to next-auth-example.
- Found the documentation helpful
- Found documentation but was incomplete
- Could not find relevant documentation
- Found the example project helpful
- Did not find the example project helpful
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:15 (8 by maintainers)
Top Results From Across the Web
RangeError: Maximum call stack size exceeded with log ...
Got following exception: RangeError: Maximum call stack size exceeded when used with log.debug(Some message", {m: metadata}); ...
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
If you see the “Maximum Call Stack Size Exceeded” error, there's likely a problem with a recursive function within your JavaScript code.
Read more >RangeError: Maximum call stack size exceeded
In this shot, we will see how to fix the “RangeError: Maximum call stack size exceeded” error. ... The most common source for...
Read more >Avoid Maximum call stack size exceeded in JavaScript
Overview · Error Maximum call stack size exceeded is raised when calling a recursive function in a loop · This is expected –...
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
🙏 For anyone interested, here was the problem 🤦, totally unintentional:
I have no time to provide a reproduction now but I can tell you that, commenting out the content of the
warn
function in thesrc/lib/logger.js
file, solves the issue.