Liang Gong

@unlikelyzero The PR needs to change the heap dump directory structure a little bit and add a static `snap-seq.json` file. I left [a comment](https://github.com/nasa/openmct/pull/6963/files/23ed6e15c190823b60902ad1ee8203e0f571b341#r1298819250) in [your openmct PR](https://github.com/nasa/openmct/pull/6963/files/23ed6e15c190823b60902ad1ee8203e0f571b341). This should...

@dennyak47 You can import and call this API to take heap snapshot from node.js: https://facebook.github.io/memlab/docs/api/modules/heap_analysis_src/#takenodefullheap In your case, just take three heap snapshots when the memory footprint is rising. For...

@FexileTV Would it be possible for you to share the 1.9GB snapshot? Or, as an alternative, could you get a smaller snapshot that still reproduces the problem?

Without a repro of the issue, it will be challenging to identify the root cause and to validate the fix. The execution appears to stall at the dominator tree construction...

The current JavaScript heap parser is not very good at processing very large heap snapshots, since memory leaks could often be captured by much smaller snapshots in most of use...

`"--headless='new'"` - Not 100% sure if this is the problem, but this seems to be the new headless mode that puppeteer is testing. Could you try `--headless=true` and see if...

@doteric Feel free to create a PR, I am happy to review it

@doteric I left a comment on the PR.

@doteric Please check and accept the CLA agreement so I can import and integrate your PR. https://github.com/facebook/memlab/blob/main/CONTRIBUTING.md#contributor-license-agreement-cla

Closing this as the PR is released in `[email protected]` .