[Heartbeat] Check for free memory before starting synthetic browser

[andrewvc]

Starting a synthetic browser requires considerably more memory than a lightweight check, and the errors returned by chrome are cryptic in this situation (it often just crashes). We should do a pre-flight check for some minimum quantity of free memory, I'd recommend 750MiB and return an error if that threshold is not met. It's not perfect, but would be an improvement.

See also #32082

[elasticmachine]

Pinging @elastic/uptime (Team:Uptime)

[paulb-elastic]

Is it worth adding a param that could be used to override this (either as a switch e.g. preflight_check_memory: false, or as a value e.g. preflight_check_memory_bytes: nnn)?

[botelastic]

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

[botelastic]

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

[botelastic]

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!