Gulp-typescript out of memory error

[skhilliard]

I recently tried to update an package for my Node.js project (mongoose 5.3.12), and it seems to have pushed me over the edge for memory during the typescript compilation phase (using gulp-typescript 5.0.1). Here is the error I see...

[18:24:13] Starting 'node_ts'...

<--- Last few GCs --->

[480:0x58548e0] 225969 ms: Mark-sweep (reduce) 2040.9 (2051.1) -> 2039.9 (2051.8) MB, 2662.0 / 0.0 ms (average mu = 0.095, current mu = 0.003) allocation failure scavenge might not succeed
[480:0x58548e0] 225977 ms: Scavenge (reduce) 2040.9 (2050.8) -> 2040.0 (2051.8) MB, 2.9 / 0.0 ms (average mu = 0.095, current mu = 0.003) allocation failure

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 0xa389b0 node::Abort() [gulp default --semVer=21.11.0.72]
2: 0x96e0af node::FatalError(char const*, char const*) [gulp default --semVer=21.11.0.72]
3: 0xbb7a4e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [gulp default --semVer=21.11.0.72]
4: 0xbb7dc7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [gulp default --semVer=21.11.0.72]
5: 0xd73fd5 [gulp default --semVer=21.11.0.72]
6: 0xd74b5f [gulp default --semVer=21.11.0.72]
7: 0xd8299b v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [gulp default --semVer=21.11.0.72]
8: 0xd8655c v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [gulp default --semVer=21.11.0.72]
9: 0xd54c3b v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [gulp default --semVer=21.11.0.72]
10: 0x109d21f v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [gulp default --semVer=21.11.0.72]
11: 0x1446379 [gulp default --semVer=21.11.0.72]
Aborted (core dumped)
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! evolved@1.0.0 build-prod: gulp default "--semVer=21.11.0.72"

I am sure this is newbie question, but do I have options to increase available memory? From what I understand this docker image has 6 GB of physical memory and 13 GB of total memory.

Any suggestions or advice would be greatly appreciated.

Thanks,
Kelly

[miketimofeev]

Hey @skhilliard!
What docker image do you mean? Our hosted VMs has 7Gb of total ram.
I think you can try to increase the max heap, something like this https://stackoverflow.com/questions/38558989/node-js-heap-out-of-memory

[miketimofeev]

You can also play around with the options for the container https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontaineroptions, there is a memory option at least

[skhilliard]

Yes....I can build locally (on my Windows box) with Visual Studio Code with no issues at all. The build is failing in the Azure Pipeline only.

[skhilliard]

Just FYI....I added this command to the build scripts to validate how much memory is available...

grep MemTotal /proc/meminfo

...and it did report 7 GB was there, which is consistent with your comment, @miketimofeev .

I am not sure why setting the environment variable...

NODE_OPTIONS=--max-old-space-size=6144

...didn't work. Are there other things that have to be done to have memory available to tsc?

[dmitry-shibanov]

Hello @skhilliard. Could you please create an issue and provide public repository to investigate dipper or simple repro steps to reproduce the issue ?

[skhilliard]

@dmitry-shibanov Sorry for the late reply, but have been busy with moving and then the holidays hit. I did as you suggested and created an issue: #4649

Let me know what other information I can provide to help.

Thanks,
Kelly