mark-sweep | A simple mark-sweep garbage collector in C

I am importing firestore like this

I'm trying to run yarn start but get this:

Starting the development server...

ts-loader: Using typescript@3.9.10 and C:\DevTools\git\mymoto\tsconfig.json

<--- Last few GCs --->

[9076:000001F4910F0DA0] 120343 ms: Mark-sweep (reduce) 2045.0 (2051.8) -> 2044.3 (2053.0) MB, 1410.7 / 0.0 ms (average mu = 0.123, current mu = 0.011) allocation failure scavenge might not succeed [9076:000001F4910F0DA0] 122662 ms: Mark-sweep (reduce) 2045.4 (2052.0) -> 2044.6 (2053.0) MB, 2288.3 / 0.0 ms (average mu = 0.057, current mu = 0.013) allocation failure scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory 1: 00007FF79BA7021F napi_wrap+109311 2: 00007FF79BA15286 v8::internal::OrderedHashTable::NumberOfElementsOffset+33302 3: 00007FF79BA16056 node::OnFatalError+294 4: 00007FF79C2E054E v8::Isolate::ReportExternalAllocationLimitReached+94 5: 00007FF79C2C53CD v8::SharedArrayBuffer::Externalize+781 6: 00007FF79C16F85C v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1516 7: 00007FF79C17AB9A v8::internal::Heap::ProtectUnprotectedMemoryChunks+1258 8: 00007FF79C177D49 v8::internal::Heap::PageFlagsAreConsistent+2457 9: 00007FF79C16C971 v8::internal::Heap::CollectGarbage+2033 10: 00007FF79C16AB75 v8::internal::Heap::AllocateExternalBackingStore+1317 11: 00007FF79C18AF67 v8::internal::Factory::NewFillerObject+183 12: 00007FF79BEBAFF1 v8::internal::interpreter::JumpTableTargetOffsets::iterator::operator=+1409 13: 00007FF79C368EFD v8::internal::SetupIsolateDelegate::SetupHeap+463949 14: 000001177FAE26D4

I've seen a few questions on here they all seem to suggest something along the lines of node --max_old_space_size=8048. In most cases the question has highlighted the code which causes this. I can't figure out what this is. How do I find out what is causing the issue? I'd like to initially see if there's anything wrong there rather than blindly trying something.

Could having a copy of my node_modules folder in the project folder cause this in any way?

I try to populate strapi database with large json file (4,6Mo),

It is working in local but when I deploy to Heroku (Hobby Basic)

I got this error:

src/index.js

My NodeJS application currently uses a Sequelize object for working across multiple stages. This object is the result of a Model.findOne operation, which includes several other models, similar to a left join with multiple tables in plain SQL.

Whenever I build using ng build I get the following error. The project I'm working on is an angular 12 with primeface template.

I've tried the following which did not work

log entry of the concurrent mark sweep garbage collector contains information like (trimmed and line breaks inserted for readability) on Java-8:

I'm reading the Garbage Collection. Algorithmis for Automatic Dynamic Memory Management book, and trying to write a blog post about it. I'm concentrating on mark-sweep chapter, where authors discuss using auxiliary stacks, to avoid mark-sweep to overflow the 'normal' stack. So far so good.

In the subchapter dedicated to the stack overflow of the auxiliary stack, there'a a direct quote:

Knuth handles overflow by treating the marking stack circularly, stacking pointers to nodes modulo h, where h is the fixed size of the stack. This means that older branch-point information on the stack is overwritten when the stack index grows larger than h. Consequently, the stack may become empty before the marking process is complete as the live graph below a node whose pointer on the mark stack has been overwritten may not have been marked.

As far as I understand it, GC process goes through the objects starting from the roots, adding pointers to the auxiliary stack. That's easy. However, this stack has a specific size (which is to prevent the overflow). When the situation occurs, that adding new pointers to this stack will be greater than the limit (resulting in SO), existing entries are discarded to make room for the new ones. That's how I understand this.

My problem is with this sentence:

Consequently, the stack may become empty before the marking process is complete as the live graph below a node whose pointer on the mark stack has been overwritten may not have been marked.

English is not my native language, and topic discussed here is not trivial, however I just need an answer - how does this mechanism work in the light of the above sentence? Why stack should be EMPTIED, and not keeping constant <= h amount of entries?

PS. In the second book of Jones - 'The Garbage Collection Handbook' there's no word about the above topics, so unfortunately I cannot compare the phrasing/preesntation.

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

I was using npm version 8.1.1 and node version 17.0.1. Then I tried downgrading to versions 7.24.2 for npm and 14.18.1 LTS for node, but I still get the same error.

I do not have a hard project, I only start it. But when I use npm run dev node js eat more than 4GB of memory and after it, I see the fatal error: