Exit Code 134 in CI: SIGABRT / abort() Explained

Exit code 134 means the process called abort() and received SIGABRT (128 + 6).

A step exiting 134 self-aborted. This is a genuine fatal error in the program, surfaced via abort().

What it means

134 = 128 + 6. abort() is raised by failed assertions, glibc heap-corruption detection, C++ std::terminate, or a runtime configured to abort on a fatal condition.

Common causes

glibc detected heap corruption (free(): invalid pointer).
A failed assert().
An unhandled C++ exception reaching std::terminate.

How to fix it

Read the stderr lines just above the abort for the exact message. This is a real, deterministic bug - reproduce it with debug symbols rather than retrying.

Related guides

Exit Codes and Signals in CI/CD: A Practical GuideA practical guide to process exit codes and signals in CI/CD - what 1, 2, 124, 126, 127, 130, 137, and 143 me… CI Exit Code Lookup: What Does This Exit Code Mean?Instant lookup for CI/CD process exit codes - enter a code (137, 127, 143…) to see what it means, whether it… Docker Build Exit Code 137 (OOM Killed) - Fix Out-of-Memory BuildsDocker build or container exiting with code 137 means the process was OOM-killed. Learn why it happens in CI…