2 Pull requests merged by 1 person

• Pulling in submodules: <ipc_shm: Fix egregiously hidden and sneaky bug/typo in SHM-classic ipc::shm::classic::Pool_arena::construct(), which also potentially affects other consumers of SHM-classic, directly or otherwise: sometimes the memory taken from a reserved SHM-pool in SHM-classic was a few bytes fewer than actually necessary, leading to unpredictable behavior for certain object sizes. / Fixed small bug wherein SHM-classic ipc::shm::classic::Pool_arena logged as-if from component TRANSPORT instead of the correct component SHM. / In SHM-classic ipc::shm::classic::Pool_arena a couple internal changes for small memory/perf improvements: the boost.ipc index is unnecessary and is now omitted; and avoid a certain heap allocation. / Minor. (Opportunistic.)>

  #147 merged Apr 11, 2025

• (SHM-jemalloc) Removed an INFO-severity logged message that is logged from ipc::shm::arena_lend::jemalloc::Ipc_arena::get_collection_id(), a public API but more likely invoked internally from Shm_session::lend_object() which can be oft-used directly and/or for each capnp-encoded message sent through a SHM-jemalloc-backed ipc::transport::struc::Channel. / Use move-semantics in a few places internally to avoid unnecessary shared_ptr ref-count arithmetic. / Effectively remove a few redundant internal assert()s. / Comment and/or doc changes.

  #144 merged Apr 10, 2025

1 Unresolved conversation

Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.

• ipc.session (+SHM-enabled): If using MQ transport in a SHM-enabled Session setup but with heap-based struc::Channel, msg size too small => barfs on moderately sized messages. / Deduced MQ msg size should be possinlenti override.

  #145 commented on Apr 4, 2025 • 0 new comments