RUNNING_OUT_OF_AVAILABLE_MEMORY
This alarm is covered by this guide. Applicable alarms (1)
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last 90 days as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm triggers when we are running out of RAM. The watermark is currently set to 5% of the total (7.8 gb) so around 380 mb.
Not having sufficient available memory could lead to catastrophic software crashes resulting in paralands. This alarm being set implies that something slipped through validation.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
all-vehicles-on-this-software-version-s{{"<small><b>Step 1</b></small><br/>Escalation: All vehicles on this software version..."}}
style all-vehicles-on-this-software-version-s fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
Resolution note
This plaintext block is ready to paste into the Resolution Note field on the ZERP issue you're working. The permalink below gives engineering review access to the full step-by-step timeline including any back-navigation; share it if the case needs a deeper look.
Permalink:
Session is too large to fit in a URL. Use Download session JSON to share the timeline out-of-band.
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.
Open pull requests
There are no open pull requests.