macOS memory-pressure checks use a built-in API and log warnings instead of throwing.
What's wrong with this entry?
On macOS, the check that retires background work under memory pressure no longer loads a system library to call sysctlbyname; it uses Bun's memory pressure API and retires at critical pressure. Failures now log a warning rather than throwing.
- Normal, warning and critical pressure map to levels 1, 2 and 4.
- Other platforms are unchanged: free memory is compared against a threshold that defaults to 1024 MB when no server value is set.
bg low-mem: memoryPressureLevel failed:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Background agent failures are labelled with a clearable reason
Both mention background agent
-
v2.1.239
Workers can register as parked instead of idle
Both mention background agent
-
v2.1.239
Background agents screen rebuilt from one large component into several
Both mention background agent