Out of memory in develop

I realize this isn’t much to go on. But I updated VSF develop to latest friday, and switched to the capybara theme and now I’m getting this fairly often (like once every hour):


[vue-i18n] Fall back to translate the keypath 'Cart' with 'en-US' locale.
HTML Minifier is enabled

<--- Last few GCs --->

[24064:000001FC1828F4B0]  2070172 ms: Mark-sweep 2020.8 (2082.7) -> 2009.7 (2083.5) MB, 2049.9 / 0.0 ms  (average mu = 0.095, current mu = 0.024) allocation failure scavenge might not succeed
[24064:000001FC1828F4B0]  2070887 ms: Mark-sweep 2024.7 (2083.5) -> 2009.5 (2083.2) MB, 686.7 / 0.1 ms  (average mu = 0.079, current mu = 0.039) allocation failure scavenge might not succeed


<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 00007FF6FDFC154D]
Security context: 0x02b2280c0921 <JSObject>
    1: /* anonymous */ [0000031AAB007DF9] [0x01b3c9b804b9 <undefined>:~1003] [pc=0000013DBCF5B80B](this=0x0142f0a3a6d1 <AST_Object map = 00000064DA579971>)
    2: _walk [0000028A827DE611] [0x01b3c9b804b9 <undefined>:~1002] [pc=0000013DBCF5AA7B](this=0x0142f0a3a6d1 <AST_Object map = 00000064DA579971>,0x026420680469 <TreeWalker map = 00000064DA57D4D1>)
    3...

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

Writing Node.js report to file: report.20200414.111030.24064.0.001.json
Node.js report completed
 1: 00007FF6FD3B0BEF napi_wrap+126287
 2: 00007FF6FD34DF26 public: bool __cdecl v8::base::CPU::has_sse(void)const __ptr64+34950
 3: 00007FF6FD34EBF6 public: bool __cdecl v8::base::CPU::has_sse(void)const __ptr64+38230
 4: 00007FF6FDB77FEE private: void __cdecl v8::Isolate::ReportExternalAllocationLimitReached(void) __ptr64+94
 5: 00007FF6FDB5F741 public: void __cdecl v8::SharedArrayBuffer::Externalize(class std::shared_ptr<class v8::BackingStore> const & __ptr64) __ptr64+785
 6: 00007FF6FDA267AC public: static void __cdecl v8::internal::Heap::EphemeronKeyWriteBarrierFromCode(unsigned __int64,unsigned __int64,class v8::internal::Isolate * __ptr64)+1468
 7: 00007FF6FDA31AF0 public: void __cdecl v8::internal::Heap::ProtectUnprotectedMemoryChunks(void) __ptr64+1312
 8: 00007FF6FDA2E5E4 public: static bool __cdecl v8::internal::Heap::PageFlagsAreConsistent(class v8::internal::HeapObject)+3188
 9: 00007FF6FDA23CF3 public: bool __cdecl v8::internal::Heap::CollectGarbage(enum v8::internal::AllocationSpace,enum v8::internal::GarbageCollectionReason,enum v8::GCCallbackFlags) __ptr64+1283
10: 00007FF6FDA22484 public: void * __ptr64 __cdecl v8::internal::Heap::AllocateExternalBackingStore(class std::function<void * __ptr64 __cdecl(unsigned __int64)> const & __ptr64,unsigned __int64) __ptr64+1396
11: 00007FF6FDA44554 public: class v8::internal::Handle<class v8::internal::HeapObject> __cdecl v8::internal::Factory::NewFillerObject(int,bool,enum v8::internal::AllocationType,enum v8::internal::AllocationOrigin) __ptr64+196
12: 00007FF6FD79E841 public: class v8::internal::interpreter::JumpTableTargetOffsets::iterator & __ptr64 __cdecl v8::internal::interpreter::JumpTableTargetOffsets::iterator::operator=(class v8::internal::interpreter::JumpTableTargetOffsets::iterator && __ptr64) __ptr64+1681
13: 00007FF6FDFC154D public: virtual bool __cdecl v8::internal::SetupIsolateDelegate::SetupHeap(class v8::internal::Heap * __ptr64) __ptr64+517453
14: 0000013DBCF5B80B
error Command failed with exit code 134.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Anyone else have this or know what could cause it? I have no real changes in VSF to cause this. (This is windows, if it matters)

look like you’re out of RAM. Can you check that first?
the easiest way to reproduce would be:

  • run the JS application
  • fire as many windows applicaitons you can, using all the RAM available
  • see if you encounter this then

If yes, you need to buy more RAM for your workstation.

1 Like

Perfectly fair answer. As I said, it’s not much to go on, it didn’t show till I updated/switched. The machine has more than enough memory available, but if nobody noticed, something must be spiking it locally sometimes.

@gibkigonzo can you please take a look?