You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We have an OpenAPI spec that is ~800KB (see attached). When trying to load it with the RedocStandalone component we're getting a long loading icon that then crashes the tab. Other smaller specs do not have the same problem. While trying to debug this I've noticed that each rendered MenuItem component seems to increase the memory usage by 10's of MB. This seems like a bug in the library implementation and is incredibly difficult to debug locally because of the minified files. In the video and screenshots below you can see the memory utilization of the tab after each render cycle (bottom left corner - JS heap size
I'm unsure what is the root cause of this but it might be related to #696 which has been open for 5 years... I would really appreciate your response and investigation on this.
Expected behavior
Memory usage of the library - even for large configurations - should not be gigabytes of memory.
Hi Gilad, this is expected. The community edition doesn't support pagination. Because of that, there is a practical limit on the size of the OpenAPI definition.
I checked the stats on the API and it's a substantial size:
Hi Adam, do you have an exact number for the limit of the definition that I could share with our stakeholders? They might be willing to pay for the paid version of Redoc if I can give them the limitations and compare that with the pricing of the product.
The API example does belong to Vindicia, I am contacting on their behalf but as an engineer of Zoomin.
Thank you for your answer regardless!
Describe the bug
We have an OpenAPI spec that is ~800KB (see attached). When trying to load it with the RedocStandalone component we're getting a long loading icon that then crashes the tab. Other smaller specs do not have the same problem. While trying to debug this I've noticed that each rendered
MenuItem
component seems to increase the memory usage by 10's of MB. This seems like a bug in the library implementation and is incredibly difficult to debug locally because of the minified files. In the video and screenshots below you can see the memory utilization of the tab after each render cycle (bottom left corner -JS heap size
I'm unsure what is the root cause of this but it might be related to #696 which has been open for 5 years... I would really appreciate your response and investigation on this.
Expected behavior
Memory usage of the library - even for large configurations - should not be gigabytes of memory.
Minimal reproducible OpenAPI snippet(if possible)
reproduction.zip
Screenshots
https://github.com/Redocly/redoc/assets/56221821/f63db0a1-017c-41e6-b9c8-e999742ac4a7
The text was updated successfully, but these errors were encountered: