-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Out-of-memory in development mode. #16827
Comments
Thank you for the info, @avendiart. I met the similar problem. Then rollbacked I wanted to create a new issue but I can see yours in the |
FYI, there is a problem not only on the Docs page. In special cases there is "freezing" even on Canvas page but since all the component stories are on the Docs page, this page really crashes. |
@angry-meow probably a reproduction repo with crashes in canvas would help maintainers to narrow it down. I've experienced these crashes as well as I mentioned above, but I don't have a reproduction for it available. |
@shilman, is it possible to specify the dependency version as 14.3.2? The problem still makes the work unreal. Storybook worked fine with 14.3.2. |
@angry-meow Good call. Can you open a PR for that? I can merge and release |
@shilman, yes, no problem |
@shilman Done |
For anyone coming across this issue. You can downgrade using the
|
It sounds like the maintainer of |
Hi, @angry-meow perfect work, by the way, could you please share the process of how to location this problem. Curiosity of Pure Private Learning, thank you! |
Describe the bug
Out-of-memory in development mode. Static build works fine.
To Reproduce
Check out https://github.com/avendiart/storybook-issue, first commit is without the crash, the latest crashes. Start storybook, switch to the
Buttons
story toDocs
. Please note, that is the most minimal reproduction I could come up with. With a different storybook, which I unfortunately can't share, crashes without even switching to the tab.System
Additional context
I've managed to pinpoint the issue to
react-element-to-jsx-string
starting from version14.3.3
. I'd assume that either the library itself or one of it's dependencies causes the crash.The text was updated successfully, but these errors were encountered: