Postman-CLI crash - JavaScript heap out of memory

My question:

I’ve installed and am using the Postman-CLI on my windows machine. It crashed when it got to my 2 of 3 iteration. I’m getting this message: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory

Details (like screenshots):

Here’s what I have in CMD (what dumped out at the crash)

<--- Last few GCs --->

[30876:0000022B2BE51110]   992724 ms: Mark-sweep (reduce) 2046.6 (2074.6) -> 2044.4 (2067.4) MB, 23.6 / 0.0 ms  (+ 49.1 ms in 24 steps since start of marking, biggest step 10.7 ms, walltime since start of marking 85 ms) (average mu = 0.808, current mu = 0[30876:0000022B2BE51110]   992826 ms: Mark-sweep (reduce) 2046.0 (2068.1) -> 2044.0 (2067.8) MB, 93.5 / 0.0 ms  (average mu = 0.665, current mu = 0.078) allocation failure scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 00007FF68E76848F v8::internal::CodeObjectRegistry::~CodeObjectRegistry+114399
 2: 00007FF68E6F68E6 DSA_meth_get_flags+65542
 3: 00007FF68E6F779D node::OnFatalError+301
 4: 00007FF68F02C3BE v8::Isolate::ReportExternalAllocationLimitReached+94
 5: 00007FF68F01699D v8::SharedArrayBuffer::Externalize+781
 6: 00007FF68EEB9D7C v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1468
 7: 00007FF68EEB6E94 v8::internal::Heap::CollectGarbage+4244
 8: 00007FF68EEB4810 v8::internal::Heap::AllocateExternalBackingStore+2000
 9: 00007FF68EED9396 v8::internal::Factory::NewFillerObject+214
10: 00007FF68EC0B865 v8::internal::DateCache::Weekday+1797
11: 00007FF68F0BA0B1 v8::internal::SetupIsolateDelegate::SetupHeap+494417
12: 0000022B2DEB9674

How I found the problem:

running the Postman-cli.exe normally

I’ve already tried:

I can just do 1 iteration at a time but that’s very manual


Please let me know what I can do to fix or troubleshoot this issue — this thing “sometimes” happens in the GUI as well, in those cases the whole client just crashes/closes

@douglasmccormickjr We are checking this issue at our end, and will you updated.
Couple of questions that will help us understand this better:

  1. Are there environment or global variables that you are using with the run. If yes, could you briefly describe the same (size or number of such variables)
  2. The collection that you are trying to run- is this happening with collection that you would describe as huge (high count of requests for example)
  3. Anything else that you would like to provide that will help us in understanding this issue better.

We have also seen this reported on our Github issue tracker (Large collections slow in runner UI · Issue #7201 · postmanlabs/postman-app-support · GitHub
Postman shuts down automatically when running a collection · Issue #8602 · postmanlabs/postman-app-support · GitHub
Slow application consuming a lot my memory and system CPU · Issue #7294 · postmanlabs/postman-app-support · GitHub)
If you find your problem relating to any of the above, feel free to check them out too.