HEART performance.memory-exhausted H-05004
Memory exhausted. Memory is (nearly) used up.
| Code | HEART performance.memory-exhausted; inside a message "code": "performance.memory-exhausted" |
|---|---|
| H-number | H-05004: area 05, code 004 |
| Area | performance: Speed, load, heat |
| Typical severity | error. A product may set another for its own case. |
| Applies to | Servers, apps, gateways, controllers with an operating system |
Likely causes
- A memory leak in a program.
- A cache allowed to grow without limit.
- More load than the memory was sized for.
- Too many programs on a small device.
How to fix or prevent it
- Find which program uses the memory.
- Restart it to recover memory now.
- Limit cache sizes, and fix or update a program that leaks.
- Add memory, or move work to a larger machine.
What the HEART does by itself
It raises an error alert at the product's limit, such as 90 % used. A Playbook may clear a cache or restart the component that holds the memory, within its guards and interlocks (for example only if the cache is not doing its job). It resolves when use falls back.
When to call service
If it comes back within hours after a restart: that points to a leak.
Related codes
software.crashedH-06002: Crashedperformance.slowH-05001: Responses slowsystem.heart-unwellH-01005: The HEART itself is unwell
Inside a message a code is written bare, "code": "storage.full". In logs, tickets, documents and searches it is written
HEART storage.full. Things that simply happen, such as system.started, are event types, not faults.
The codes are defined in Part 3, Section 5.4, and their H-numbers in Section 5.7.
All of it, as data: fault-codes.json.
All fault codes, by area · All fault codes, by H-number · Problem types (API errors)