Cypress Server process memory between spec files remains unresolved in Cypress 14

Cypress 14 raises the Node engine requirement to 18 or later for cypress open and cypress run, and Component Testing bundler defaults shifted from webpack based defaults toward Vite compatible configuration between Cypress 13 and 14. Test Isolation default behavior changed in Cypress 12.x to per test browser context reset.

Memory growth in long running cypress run sessions is a reported behavior with Chrome based browsers when video recording and screenshots are enabled simultaneously, with no definitive automatic mitigation shipped in stable releases. Cypress has not published a final decision on automatic garbage collection for the Cypress Server process between spec files, leaving teams to choose manual process restarts for large suites as an unresolved operational decision.

For planning CI images and local development with Cypress 14.x on Node 18+, the intended Server process lifecycle across spec boundaries needs clarification.

Is automatic garbage collection or process recycling for the Cypress Server between spec files planned for a future Cypress release? What configuration signals currently control Server process memory handling between spec files in Cypress 14? How does the Node 18+ engine requirement interact with the Server process lifecycle across spec files in cypress run?