-
-
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
Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory #7092
Comments
Maybe related: #6408 |
This might be an easy win: #7091 |
Hi there ! Jumping in to say we encountered the same thing here -- and that deactivating Source Maps worked for us as a workaround. |
@shilman you mean finding there is one bad library which causes the issue? I don't think I added some library to my bundle in the past, I just think the bundle got too big over time. Any recommendations on how to apply code splitting here? :) |
@rwieruch I mean that fix is going to reduce the bundle size by 5% or so. It's a small thing, but small things add up. I'm hoping we can do a perf sprint at some point soon and improve the situation. |
Our team encountering the same issue. BTW Upgrading from Node v10 to v12 made it occur less often. |
cc @ndelangen |
@rwieruch In a separate issue we discovered the |
@shilman I didn't run into the problem anymore, because I extracted a larger part of the UI library into a separate library (Icons). This fixed the issue for me. Unfortunately I cannot revert to an older version at the moment to verify source-loader for causing the issue. |
@shilman I think we fixed this in the source-loader, right? |
I'm having the same issue.
Any other solution then extracting some of my stories? |
@nicholasbraun Can you try upgrading to |
@shilman It works on my local machine, but not on the server where I deploy it to. It has only 2GB of memory. |
@nicholasbraun So it's the same behavior on 5.1.10 and 5.2.0-beta.28? |
@shilman yes. |
@nicholasbraun Are you using |
@nicholasbraun and I were able to work around the issue by removing react docgen. I added an issue to fix this properly: #7743 |
Any other tricks to get this working on storybook 5.1.11? I recently updated my build size, and I'm seeing this, despite increasing
My webpack config:
Start-storybook still works fine; disabling the minification altogether would also be an option. Would that be done with |
My Storybook project has grown to a larger size and on
I get the following Stack Trace [0] with a custom Webpack config [1]. It happens on the recent v5.1.4 but also on an older v5.0.x. I guess it isn't related to the Storybook version, but just to the size of my project. What's the recommended strategy to take from here?
Happy to receive any hints on how to proceed if running into this issue.
Node: v10.16.0
Machine: MacOS
[1] Custom webpack.config.js for Storybook:
[0] Stack Trace:
[2] Deactivate Source Maps?
Works, but shouldn't be the solution, should it?
Since the build succeeds with this configuration, for the sake of completeness, my bundle size:
The text was updated successfully, but these errors were encountered: