![]() ![]() Heap allocated 7.8 GB Heap allocated 7.81 GB 45701 ms: Mark-sweep (reduce) 8000.2 (8005.3) -> 8000.2 (8006.3) MB, 1468.4 / 0.0 ms (average mu = 0.211, current mu = 0.000) last resort GC in old space requested FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory The V8 garbage collector has a -max-old-space-size parameter available to the Node executable: Theoretically, a 64-bit process should be able to allocate more than 4GB and grow comfortably well into 16 terabytes of address space. These results suggest that the memory limit might have carried over from legacy code.Īt the time of writing, the script ran under the latest LTS Node version and is using a 64-bit executable. The V8 garbage collector originally ran in a 32-bit browser process with strict memory restrictions. The reasons for this are somewhat unknown. This process hits a 4.1GB limit and takes 26.6 seconds to realize it was time to die. Here, the garbage collector attempts to compact memory as a last resort before giving up and throwing a 'heap out of memory' exception. ![]() Heap allocated 4 GB Heap allocated 4.01 GB 26146 ms: Mark-sweep (reduce) 4103.7 (4107.3) -> 4103.7 (4108.3) MB, 1196.5 / 0.0 ms (average mu = 0.112, current mu = 0.000) last resort GC in old space requested FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |