What does the grey color represents in above chart?
Use memory profiling in inspector Run node with --inspect flag and open the inspector. The simplest way to get a Heap Snapshot is to connect a inspector to your process running locally. Then go to Memory tab and take a heap snapshot.
To find out how much memory different pages use, you should open the built-in Chrome Task Manager. After opening the Chrome Memory tab, you are introduced with three options to investigate website's memory usage: you can take a heap snapshot, start allocation instrumentation on a timeline, or begin allocation sampling.
This is the outcome when you open multiple tabs in your browser, which in turn uses more RAM. Therefore, it may freeze or hang your device for a few minutes. Anyway, without wasting any time let's see How to Fix Chrome Memory Leak & reduce high RAM usage with the help of the below-listed tutorial.
This command allows you to take a snapshot of how your heap memory is distributed among your page's JavaScript objects and related DOM nodes, which then can be loaded into Chrome DevTools to analyze and find any memory leaks.
Total Memory: 20,526 KB
Total Allocated Memory: 1925 + 2939 + 2918 + 494 + 840 = 9,116 KB
Total Unallocated Memory: 20,526 - 9,116 = 11,410 KB
11410 / 20526 = ~0.56 (0.56/1) which is the area shaded on the graph.
Total Unallocated Memory / Total Memory = Shaded Area
Doughnut chart showing allocated memory vs unallocated memory
In a represented Heap Snapshot Statictics
pie chart –
TOTAL is a total memory heap distribution between JavaScript objects and associated DOM nodes. Also I should say that the heap is a memory set aside for dynamic allocation.
According to Chrome Memory Tab article:
Memory leaks occur when a website is using more energy than necessary. Severe memory leaks can even make sites unusable. Since the JavaScript memory leak detector is a part of the Google Chrome browser, you should not hesitate to select a profiling type and analyze your website’s memory usage.
Google Chrome heap snapshot will reveal memory distribution between JavaScript objects and associated DOM nodes. This feature is useful because you will be able to compare different snapshots and find memory leak.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With