Skip to content
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

Open
korthout opened this issue Feb 28, 2024 · 1 comment

Comments

@korthout
Copy link

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

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

Prepare all required actions
Getting action download info
Download action repository 'test-summary/action@v[2](https://github.com/camunda/zeebe/actions/runs/8079356898/job/22073590049#step:8:2)' (SHA:0[3](https://github.com/camunda/zeebe/actions/runs/8079356898/job/22073590049#step:8:3)2c8a9cec6aaa3c20228112cae6ca10a3b29336)
Run ./.github/actions/analyze-test-runs
  with:
    buildOutputFilePath: /tmp/tmp.LOTa7DADOL
  env:
    DOCKER_PLATFORMS: linux/amd6[4](https://github.com/camunda/zeebe/actions/runs/8079356898/job/22073590049#step:8:4),linux/arm64
    ARTIFACTS_USR: ***
    ARTIFACTS_PSW: ***
    REGISTRY_HUB_DOCKER_COM_USR: ***
    REGISTRY_HUB_DOCKER_COM_PSW_READ_ONLY: ***
    JAVA_HOME: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/21.0.2-13.0.LTS/x64
    JAVA_HOME_21_X64: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/21.0.2-13.0.LTS/x64
    BUILD_OUTPUT_FILE_PATH: /tmp/tmp.LOTa7DADOL
Run test-summary/action@v2
  with:
    paths: **/target/failsafe-reports/TEST-*.xml
  **/target/surefire-reports/TEST-*.xml
  
  env:
    DOCKER_PLATFORMS: linux/amd64,linux/arm64
    ARTIFACTS_USR: ***
    ARTIFACTS_PSW: ***
    REGISTRY_HUB_DOCKER_COM_USR: ***
    REGISTRY_HUB_DOCKER_COM_PSW_READ_ONLY: ***
    JAVA_HOME: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/21.0.2-13.0.LTS/x64
    JAVA_HOME_21_X64: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/21.0.2-13.0.LTS/x64
    BUILD_OUTPUT_FILE_PATH: /tmp/tmp.LOTa7DADOL

<--- Last few GCs --->

[30170:0x6beb9[5](https://github.com/camunda/zeebe/actions/runs/8079356898/job/22073590049#step:8:5)0]    321[6](https://github.com/camunda/zeebe/actions/runs/8079356898/job/22073590049#step:8:6)8 ms: Scavenge 4039.6 (4110.9) -> 4040.3 (4111.[7](https://github.com/camunda/zeebe/actions/runs/8079356898/job/22073590049#step:8:7)) MB, 9.06 / 0.00 ms  (average mu = 0.166, current mu = 0.110) allocation failure; 
[30170:0x6beb950]    321[8](https://github.com/camunda/zeebe/actions/runs/8079356898/job/22073590049#step:8:8)1 ms: Scavenge 4040.4 (4111.7) -> 403[9](https://github.com/camunda/zeebe/actions/runs/8079356898/job/22073590049#step:8:9).5 (4134.9) MB, 12.24 / 0.00 ms  (average mu = 0.166, current mu = 0.1[10](https://github.com/camunda/zeebe/actions/runs/8079356898/job/22073590049#step:8:10)) allocation failure; 
[30170:0x6beb950]    35937 ms: Mark-Compact 4055.2 (4134.9) -> 4055.2 (4134.9) MB, 3745.20 / 0.00 ms  (average mu = 0.093, current mu = 0.018) allocation failure; scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0xc99960 node::Abort() [/runner/externals/node20/bin/node]
 2: 0xb6ffcb  [/runner/externals/node20/bin/node]
 3: 0xebe910 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/runner/externals/node20/bin/node]
 4: 0xebebf7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/runner/externals/node20/bin/node]
 5: 0x10d06a5  [/runner/externals/node20/bin/node]
 6: 0x10d0c34 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/runner/externals/node20/bin/node]
 7: 0x10e7b24 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/runner/externals/node20/bin/node]
 8: 0x10e833c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/runner/externals/node20/bin/node]
 9: 0x10be641 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/runner/externals/node20/bin/node]
10: 0x10bf7d5 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/runner/externals/node20/bin/node]
[11](https://github.com/camunda/zeebe/actions/runs/8079356898/job/22073590049#step:8:11): 0x109cd46 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/runner/externals/node20/bin/node]
[12](https://github.com/camunda/zeebe/actions/runs/8079356898/job/22073590049#step:8:12): 0x14f7b76 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/runner/externals/node20/bin/node]
[13](https://github.com/camunda/zeebe/actions/runs/8079356898/job/22073590049#step:8:13): 0x78a963ed9ef6 
Run if [ ! -s "$BUILD_OUTPUT_FILE_PATH" ]; then

@megglos
Copy link

megglos commented Mar 7, 2024

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants