Run with leakage on refresh:
npm run leak - refreshes every one second with affinity on to demonstrate leakage
Run without leakage:
npm start will not leak
Run with leakage on close:
npm run closeleak - closes and reopens with the same affinity to demonstrate leakage
Run with random affinity on each close:
npm run fixcloseleak - closes and reopens with different affinity each time to remove leakage
Run with intentional process crashing every 5th close:
npm run crash - crashes the render process every 5th close in order to reclaim affinity memory
Leakage occurs if affinity is used. Each refresh will leak ~1.5Mb memory.
It's worth noting that "leaked memory" is defined as "memory not yet garbage collected"
From what I can tell, when affinity is on, the leaked memory in renderer process is never garbage collected.
Just add entry in constants.js with the property from memory data
path is used to locate the value of the property in the memory data
name is used to prefix the report output
Heap snapshots are taken in the renderer process at every refresh and written to disk
Includes:
webFrame: webFrame.getResourceUsage(),
processHeap: process.getHeapStatistics(),
processMemUsage: process.memoryUsage(),
processMemoryInfo: process.getSystemMemoryInfo(),
Includes:
memObject.processHeap = process.getHeapStatistics();
memObject.processMemoryInfo = process.getSystemMemoryInfo();
memObject.processMemUsage = process.memoryUsage();