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
JavaScript heap out of memory #123
Comments
hey @dennishn I haven't seen this error building the portfolio and I've done it quite a few times, can you maybe specify which node version are you using? Is maybe that th issue? Or can you help me reproduce somehow? |
Hey @matjack1 - the issue is not the gatsby-portfolio, it's just the easiest way to reproduce it using your gatsby example repository. It's important to note that this happens with our DatoCMS content - I can share our API token with you via email. I don't think this is a node issue, i've tried using v10.17.0, v12.16.1 and v14.4.0 and the issue happens on all versions. |
Yes @dennishn, please reach to us giving us the name of your project at least :D https://www.datocms.com/support?topics=technical-support/ive-found-a-bug Edit: corrected the link :) |
@dennishn @stefanoverna I can reproduce the same issue, we are going to have a look at this and let you know as soon as possible. |
Thank you very much friends :) |
Hey @dennishn, can you please try v2.5.1 and see if it works? |
@stefanoverna Unfortunately no luck - still getting the heap out of memory error.
Will try to find time to dig deeper |
On my machine it works :/ |
This is in fact very likely gatsby core issue. I got my hand on one reproductions and was able to make some quick hanges in gatsby core to prevent this (for validation purposes - those changes need to be done properly and not in hacky way). In any case I opened gatsbyjs/gatsby#28916 in gatsby repo to track this issue (as this is not Datocms specific issue) |
awesome, thanks! |
Ok, found particular culrpint and workaround (at least until we ship it in stable gatsby). The extra memory usage (and actually cpu perf overhead) comes from http://bluebirdjs.com/docs/api/promise.longstacktraces.html in |
closing this one to avoid duplicates |
Hello, for some time we have had issues using the gatsby-source-datocms without running into out-of-memory issues.
We have been able to get past this by increasing allowed memory for node - but we are now seeing this happening across more environments (CI envs, OSX and Windows).
Using your gatsby-portfolio example project, using our projects API key and running the
gatsby develop
task - we get the following out-of-memory error:We've also seen this happen for production builds (
gatsby build
) - but this happens more irregularly.The easiest way to reproduce is cloning https://github.com/datocms/gatsby-portfolio and setting the
DATO_API_TOKEN
- please reach out for this or let me know how I can send it to you.It does look like out-of-memory issues are happening across Gatsby plugins:
gatsbyjs/gatsby#15190
gatsbyjs/gatsby#15256
gatsbyjs/gatsby#15540
But most of those issues seems be resolved by either:
gatsby-netlify-cms
package - obviously not feasible for us either :DThe text was updated successfully, but these errors were encountered: