-
Notifications
You must be signed in to change notification settings - Fork 32
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
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory #45
Comments
14 tasks
related to #5 |
megglos
added a commit
to camunda/camunda
that referenced
this issue
Mar 7, 2024
It currently runs into a limitation due to the amount of data. See test-summary/action#45 .
megglos
added a commit
to camunda/camunda
that referenced
this issue
Mar 7, 2024
It currently runs into a limitation due to the amount of data. See test-summary/action#45 .
megglos
added a commit
to camunda/camunda
that referenced
this issue
Mar 7, 2024
It currently runs into a limitation due to the amount of data. See test-summary/action#45 .
megglos
added a commit
to camunda/camunda
that referenced
this issue
Mar 7, 2024
It currently runs into a limitation due to the amount of data. See test-summary/action#45 . (cherry picked from commit f28d938)
megglos
added a commit
to camunda/camunda
that referenced
this issue
Mar 7, 2024
It currently runs into a limitation due to the amount of data. See test-summary/action#45 . (cherry picked from commit f28d938)
megglos
added a commit
to camunda/camunda
that referenced
this issue
Mar 7, 2024
It currently runs into a limitation due to the amount of data. See test-summary/action#45 . (cherry picked from commit f28d938)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This error was reported by Node while running this action in https://github.com/camunda/zeebe/actions/runs/8079356898/job/22073590049
Some other projects (like this one) avoid this issue by just allowing a bit more memory for node using node_options. But, it might hide an underlying issue that should be investigated.
Full Logs
The text was updated successfully, but these errors were encountered: