🐛 Insufficient Heap Memory During Build

[kneerose]

Context

• During the npm run build process, the following error occurs:
  FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory.
• As a result, the test stack deployment is stuck and not synchronized with the latest updates.
• The failure can be observed in the test stack: Test Stack Failure.

Actual behavior

<--- Last few GCs --->

[1486016:0x61c0320]    27122 ms: Mark-Compact (reduce) 2046.3 (2081.6) -> 2045.9 (2082.3) MB, 448.85 / 0.01 ms  (+ 56.0 ms in 13 steps since start of marking, biggest step 5.1 ms, walltime since start of marking 517 ms) (average mu = 0.357, current mu = 0[1486016:0x61c0320]    27863 ms: Mark-Compact (reduce) 2046.6 (2082.3) -> 2046.3 (2082.8) MB, 614.20 / 0.00 ms  (+ 0.0 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 622 ms) (average mu = 0.265, current mu = 0.1

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 0xb86ecf node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
 2: 0xef74d0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 3: 0xef77b7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 4: 0x1109355  [node]
 5: 0x11211d8 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 6: 0x10f72f1 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 7: 0x10f8485 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 8: 0x10d4ba6 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [node]
 9: 0x10c631c v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawArray(int, v8::internal::AllocationType) [node]
10: 0x10c6484 v8::internal::FactoryBase<v8::internal::Factory>::NewFixedArrayWithFiller(v8::internal::Handle<v8::internal::Map>, int, v8::internal::Handle<v8::internal::Oddball>, v8::internal::AllocationType) [node]
11: 0x13f623d v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Allocate(v8::internal::Isolate*, int, v8::internal::AllocationType) [node]
12: 0x13f62e3 v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Rehash(v8::internal::Isolate*, v8::internal::Handle<v8::internal::OrderedHashMap>, int) [node]
13: 0x1526ef3 v8::internal::Runtime_MapGrow(int, unsigned long*, v8::internal::Isolate*) [node]
14: 0x760af54d9ef6 
Aborted (core dumped)

Expected behavior

The build process should complete successfully without encountering an out-of-memory error.

Suggestion

Increase the heap memory allocation in the Dockerfile before initiating the build.

[bosko-m]

@kneerose is it PDF or Voting/Delegation? Cause it says pdf pillar and is assigned to @MSzalowski

[kneerose]

@bosko-m , I apologize for assigning the wrong label earlier. The issue is neither related to the voting/delegation, nor the proposal pillar. Instead, it is specifically associated with the frontend code build setup. which is failing on docker setup npm run build.

[kneerose]

@MSzalowski The issue is still not resolved: GitHub Actions Run Link.

• When I attempt to build the Docker file from the code, it continues to show a "heap out of memory" error
  

[kneerose]

@MSzalowski The issue is still not resolved yet : GitHub Actions Run Link.

--max-old-space-size=4096
Increasing the Node space to 4GB is not enough

[kneerose]

• GitHub Actions Run Link. This issue is due to the storybook build I have increased the heap memory limit on the storybook, and it is fixed now.
• GitHub Actions Run Link
  CC: @bosko-m