Capacity Exceeded error in stomach component

The goal is to determine how the stomach component manages static memory pools when multiple TeX requests are executed concurrently, resulting in the documented Capacity Exceeded error.

TeX operates as a single-threaded engine; concurrency is achieved by launching separate OS processes, each with its own static allocation for buffers such as main_size and pool_size. The page builder's glue and penalty calculation decide line and page breaks.

• Do static memory pools remain isolated per process or are they shared across concurrent requests?
• Can the Capacity Exceeded error arise from interleaved concurrent requests without increasing per-process memory limits?
• What is the relationship between the page builder's glue and penalty calculation and the static memory allocation model under concurrent execution?