Skip to content

RangeError: Maximum call stack size exceeded #4637

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
gaurav517 opened this issue Jun 10, 2018 · 3 comments
Closed

RangeError: Maximum call stack size exceeded #4637

gaurav517 opened this issue Jun 10, 2018 · 3 comments

Comments

@gaurav517
Copy link

Q&A (please complete the following information)

  • OS: macOS
  • Browser: chrome
  • Version: 66.0.3359.181
  • Swagger-UI version: 3.13.6
  • Swagger/OpenAPI version: Swagger 2.0

In case of big nested request/response json spec, I get following in console after trying to expand the operation in swagger-ui and the section of operation shows endless spinner. After refreshing we see the operation details.

system.js:461 RangeError: Maximum call stack size exceeded
    at immutable.js:2405
    at Le.pe.withMutations (immutable.js:1353)
    at He (immutable.js:2405)
    at Le.set (immutable.js:2096)
    at nt (immutable.js:2780)
    at Ze.set (immutable.js:2686)
    at immutable.js:2651
    at immutable.js:3016
    at immutable.js:2699
    at Le.__iterate (immutable.js:2206)
@heldersepu
Copy link
Contributor

heldersepu commented Jun 10, 2018

looks like a duplicate of #4411, probably best to close this one.
And leave a note on 4411, you should also include your swagger.json
and in my experience it does not need to be a big, endless recursion or that complex to crash the UI, see the examples there, I managed to crash it with a very small spec see the: #4411 (comment)

@shockey
Copy link
Contributor

shockey commented Jun 11, 2018

Yep, this sounds like #4411 to me - closing as a duplicate, but this report will be considered when it's looked at.

As @heldersepu mentioned, crossposting your Swagger/OpenAPI document into that issue would help make sure things get fixed for you 😄

@lock
Copy link

lock bot commented Jul 1, 2019

Locking due to inactivity.
This is done to avoid resurrecting old issues and bumping long threads with new, possibly unrelated content.
If you think you're experiencing something similar to what you've found here: please open a new issue, follow the template, and reference this issue in your report.
Thanks!

@lock lock bot locked and limited conversation to collaborators Jul 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants