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 exceeded
See original GitHub issueDescribe the bug
This used to happen after a loon time and amout of failed scan attempts, but after upgrading RxJS it happens right after changing the device and the first scanFailure is fired. After that RangeError, no scan is done and the stream remains dead-like.
To Reproduce Steps to reproduce the behavior:
- Open the demo.
- Wait.
- See error
or in certain RxJS versions it may:
- Open the demo.
- See the error.
- Also happens when changing devices.
Expected behavior Not to exceed any call stack.
Screenshots
Desktop (please complete the following information):
- Device: desktop
- OS: Windows 10
- Browser: Chrome - 74.0.3729.169 64 bits
- Version: development 1.6
Additional context Add any other context about the problem here.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@odahcam, I’m still seeing this in the StackBlitz. Could this be updated?
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.