feat(test): refactor the memory usage test to use metrics from CLI process instead of test runner

[cynthialong0-0]

Summary

Refactors the memory usage monitoring and testing infrastructure to use telemetry metrics captured directly from the CLI process. This replaces the previous method of measuring the test runner's process, providing a realistic and accurate view of the application's actual memory footprint.

Details

• Updated MemoryTestHarness and MemoryUsage tests to extract RSS, Heap, and External memory metrics from the spawned CLI process telemetry via TestRig.
• Added assertMemoryReturnsToBaseline and analyzeSnapshots to the test harness to verify that large data (like chat history or tool outputs) is correctly cleaned up and to detect sustained memory leaks.
• Update baseline measurement unit from Bytes to MB for readiness

Related Issues

Fixes #25137

How to Validate

Execute npm run test:memory

Pre-Merge Checklist

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed)
• Noted breaking changes (if any)
• Validated on required platforms/methods:
  • MacOS
    • npm run
    • npx
    • Docker
    • Podman
    • Seatbelt
  • Windows
    • npm run
    • npx
    • Docker
  • Linux
    • npm run
    • npx
    • Docker

[github-actions]

Size Change: -4 B (0%)

Total Size: 33.7 MB

Filename	Size	Change
./bundle/chunk-7HZ62EWV.js	0 B	-14.5 MB (removed)	🏆
./bundle/chunk-7JYX7OYE.js	0 B	-49.2 kB (removed)	🏆
./bundle/chunk-7LSIJV5T.js	0 B	-3.8 kB (removed)	🏆
./bundle/chunk-QOIPE2QP.js	0 B	-3.43 kB (removed)	🏆
./bundle/chunk-TFETZB54.js	0 B	-674 kB (removed)	🏆
./bundle/chunk-USRW35AA.js	0 B	-2.72 MB (removed)	🏆
./bundle/core-XRKWYEBZ.js	0 B	-46.7 kB (removed)	🏆
./bundle/devtoolsService-JM7UV5K7.js	0 B	-28.4 kB (removed)	🏆
./bundle/gemini-HBHBH6VI.js	0 B	-576 kB (removed)	🏆
./bundle/interactiveCli-VGZMS7IN.js	0 B	-1.3 MB (removed)	🏆
./bundle/liteRtServerManager-56MHLN2Q.js	0 B	-2.08 kB (removed)	🏆
./bundle/oauth2-provider-UE6YCM4Y.js	0 B	-9.16 kB (removed)	🏆
./bundle/chunk-HR2ES54B.js	674 kB	+674 kB (new file)	🆕
./bundle/chunk-JAMMAQG2.js	3.43 kB	+3.43 kB (new file)	🆕
./bundle/chunk-KCOTKXAN.js	2.72 MB	+2.72 MB (new file)	🆕
./bundle/chunk-PTPTNZCW.js	14.5 MB	+14.5 MB (new file)	🆕
./bundle/chunk-QCEKEH7S.js	49.2 kB	+49.2 kB (new file)	🆕
./bundle/chunk-QQTORNYT.js	3.8 kB	+3.8 kB (new file)	🆕
./bundle/core-CHRJT6GK.js	46.7 kB	+46.7 kB (new file)	🆕
./bundle/devtoolsService-UWEWS7SV.js	28.4 kB	+28.4 kB (new file)	🆕
./bundle/gemini-F7D42O7Y.js	576 kB	+576 kB (new file)	🆕
./bundle/interactiveCli-72YQXBD5.js	1.3 MB	+1.3 MB (new file)	🆕
./bundle/liteRtServerManager-6T3X27HW.js	2.08 kB	+2.08 kB (new file)	🆕
./bundle/oauth2-provider-E5RPVIHW.js	9.16 kB	+9.16 kB (new file)	🆕

ℹ️ View Unchanged

Filename	Size	Change
./bundle/bundled/third_party/index.js	8 MB	0 B
./bundle/chunk-34MYV7JD.js	2.45 kB	0 B
./bundle/chunk-5AUYMPVF.js	858 B	0 B
./bundle/chunk-5PS3AYFU.js	1.18 kB	0 B
./bundle/chunk-664ZODQF.js	124 kB	0 B
./bundle/chunk-DAHVX5MI.js	206 kB	0 B
./bundle/chunk-IUUIT4SU.js	56.5 kB	0 B
./bundle/chunk-RJTRUG2J.js	39.8 kB	0 B
./bundle/chunk-YIPDXML5.js	1.97 MB	0 B
./bundle/cleanup-GLDYQJA4.js	0 B	-932 B (removed)	🏆
./bundle/devtools-36NN55EP.js	696 kB	0 B
./bundle/dist-T73EYRDX.js	356 B	0 B
./bundle/events-XB7DADIJ.js	418 B	0 B
./bundle/examples/hooks/scripts/on-start.js	188 B	0 B
./bundle/examples/mcp-server/example.js	1.43 kB	0 B
./bundle/gemini.js	4.97 kB	0 B
./bundle/getMachineId-bsd-TXG52NKR.js	1.55 kB	0 B
./bundle/getMachineId-darwin-7OE4DDZ6.js	1.55 kB	0 B
./bundle/getMachineId-linux-SHIFKOOX.js	1.34 kB	0 B
./bundle/getMachineId-unsupported-5U5DOEYY.js	1.06 kB	0 B
./bundle/getMachineId-win-6KLLGOI4.js	1.72 kB	0 B
./bundle/memoryDiscovery-NXEEFR74.js	980 B	0 B
./bundle/multipart-parser-KPBZEGQU.js	11.7 kB	0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/client/main.js	222 kB	0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/_client-assets.js	229 kB	0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/index.js	13.4 kB	0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/types.js	132 B	0 B
./bundle/sandbox-macos-permissive-open.sb	890 B	0 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB	0 B
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB	0 B
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB	0 B
./bundle/sandbox-macos-strict-open.sb	4.82 kB	0 B
./bundle/sandbox-macos-strict-proxied.sb	5.02 kB	0 B
./bundle/src-QVCVGIUX.js	47 kB	0 B
./bundle/start-UAYHAXS3.js	0 B	-622 B (removed)	🏆
./bundle/tree-sitter-7U6MW5PS.js	274 kB	0 B
./bundle/tree-sitter-bash-34ZGLXVX.js	1.84 MB	0 B
./bundle/cleanup-6EBSF7WT.js	932 B	+932 B (new file)	🆕
./bundle/start-ZUWTOA5U.js	622 B	+622 B (new file)	🆕

_{compressed-size-action}

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly overhauls the memory testing infrastructure to provide more accurate and realistic memory usage measurements. By shifting from monitoring the test runner to the actual CLI process via telemetry, it aims to identify and prevent memory regressions more effectively. This change also introduces new tools for detecting sustained memory leaks and verifying proper memory cleanup after large operations, ensuring the application maintains optimal performance.

Highlights

• Refactored Memory Monitoring: The memory usage monitoring and testing infrastructure has been refactored to capture telemetry metrics directly from the CLI process, replacing the previous method of measuring the test runner's process. This provides a more accurate view of the application's actual memory footprint.
• New Memory Assertions: New assertions, assertMemoryReturnsToBaseline and analyzeSnapshots, have been added to the test harness. These verify that large data (like chat history or tool outputs) is correctly cleaned up and help detect sustained memory leaks.
• Unit Change for Baselines: The baseline measurement unit for memory has been updated from Bytes to Megabytes (MB) for improved readability and readiness.
• TestRig Integration: The TestRig utility now includes methods to read memory, CPU, and event loop metrics from telemetry logs, enabling the MemoryTestHarness to leverage these for more precise measurements.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the memory testing infrastructure to utilize telemetry-based metrics instead of direct V8 heap snapshots. It updates baselines to use megabytes, enhances the TestRig to parse telemetry logs for memory, CPU, and event loop metrics, and updates the MemoryTestHarness to extract these values. A critical issue was identified in the TestRig telemetry parsing where the aggregation key lacks sub-second precision, causing significant data loss when monitoring intervals are short (e.g., 100ms).

[jacob314]