fix: adding emergency garbage collection at 90% for chromium-based browsers

[mschile]

Edit: Reverted in #25546

• Closes n/a

User facing changelog

n/a

Additional details

In an effort to reduce OOM errors, we decided to perform a GC when the browser's renderer process reaches 90% of the available memory.

Steps to test

How has the user experience changed?

n/a

PR Tasks

• Have tests been added/updated?
• Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• [n/a] Has a PR for user-facing changes been opened in cypress-documentation?
• [n/s] Have API changes been updated in the type definitions?

[cypress]

---

Test summary

26572 • 0 • 1281 • 0 • 40

---

Run details

Project	cypress
Status	Passed
Commit	6f15a10
Started	Jan 19, 2023 8:13 PM
Ended	Jan 19, 2023 8:33 PM
Duration	19:28 💡
OS	Linux Debian -
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	create-from-component.cy.ts		2
1	... > runs generated spec
2	... > runs generated spec
	commands/net_stubbing.cy.ts		3
1	network stubbing > intercepting request > can delay and throttle a StaticResponse
2	network stubbing > intercepting request > can delay and throttle a StaticResponse
3	... > with `times` > only uses each handler N times
This comment includes only the first 5 flaky tests. See all 40 flaky tests in the Cypress Dashboard.

---

This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard