audit-memory

To audit PMR allocation safety in C++ coroutine code, review hot-path memory-resource selection, container MR consistency, and frame-arena scope to catch dangling references and cross-thread resource misuse before runtime crashes.

Invalid iterator and pointer usage in C++ coroutine suspension points is caused by container growth, erase, or insert operations invalidating references after a co_await, requiring lifecycle and ownership audits of pooled objects and frame-scoped arenas.

Check frame_arena scope and pooled_object lifetime by validating memory-resource selection, pooled allocation limits, and cleanup guarantees against coroutine resume flows to prevent dangling access in hot-path networking systems.

Yes, this PMR memory safety audit works for zero-allocation hot paths and session flows by verifying cross-thread temporary allocations, container MR consistency, and coroutine resume cleanup guarantees in high-performance C++ code.

Limitations of auditing C++ coroutine object lifetime include detecting complex dangling reference risks across cross-thread resource misuse and iterator invalidation, which require validating frame-arena scope and pooled allocation limits in production behavior.