IGNORE() logs a context and never releases it #3

New Issue

tachikoma · 2026-08-02T18:53:16-04:00

tachikoma commented

2026-08-02 18:53:16 -04:00

Source: TODO.md §1.2 (at 669b2b3)

deps/libakerror/include/akerror.tmpl.h:308. The macro assigns the context to
__akerr_last_ignored, logs it, and stops. The slot is never returned to the
pool, so every IGNORE() on a failing call leaks one -- and after
AKERR_MAX_ARRAY_ERROR of them the pool is exhausted and ENSURE_ERROR_READY
calls exit(1).

Consequence here. aksl_tree_iterate's CLEANUP block (src/stdlib.c)
cannot use IGNORE() to drop a queue-drain failure and open-codes the
log-then-release by hand instead, with a comment saying why. It is four lines
that should be one.

What closing it would touch. One RELEASE_ERROR in the macro; then delete the
workaround here.

Not fixable from inside this repository.

Files: deps/libakerror/include/akerror.tmpl.h:308, src/stdlib.c

Filed by Tachikoma (Claude Code, Opus 5, 1M context)

**Source:** TODO.md §1.2 (at 669b2b3) `deps/libakerror/include/akerror.tmpl.h:308`. The macro assigns the context to `__akerr_last_ignored`, logs it, and stops. **The slot is never returned to the pool**, so every `IGNORE()` on a failing call leaks one -- and after `AKERR_MAX_ARRAY_ERROR` of them the pool is exhausted and `ENSURE_ERROR_READY` calls `exit(1)`. **Consequence here.** `aksl_tree_iterate`'s `CLEANUP` block (`src/stdlib.c`) cannot use `IGNORE()` to drop a queue-drain failure and open-codes the log-then-release by hand instead, with a comment saying why. **It is four lines that should be one.** **What closing it would touch.** One `RELEASE_ERROR` in the macro; then delete the workaround here. Not fixable from inside this repository. **Files:** `deps/libakerror/include/akerror.tmpl.h:308`, `src/stdlib.c` --- Filed by Tachikoma (Claude Code, Opus 5, 1M context)

tachikoma added this to the 0.3.0 milestone 2026-08-02 18:53:16 -04:00

tachikoma added the defect blast-radius:medium status::grooming labels 2026-08-02 18:53:16 -04:00

tachikoma referenced this issue

2026-08-02 18:57:14 -04:00

The pinned libakerror is 1.0.0 and has an unlocked error pool; 2.0.1 locks it #2

Sign in to join this conversation.