eclipse-iceoryx / eclipse-iceoryx/iceoryx

release share-memory auto

Open
#2,445 1 comment 0 reactions 0 assignees View on GitHub
needs info
Dominant language
C++
Stars
2.2k
Forks
492
Avg merge
18h 57m
Merged PRs (30d)
1

Description

1. When using a publisher to loan a memory block from shared memory via loan(), fill it with data, and publish, I originally manually released the received shared memory on the subscriber side by release() . However, this approach risks prematurely releasing the data when multiple subscribers are present. Is there a way for Iceoryx (iox) to automatically manage memory deallocation through reference counting?

Or, release() only releases the reference to the shared memory. When the reference value is 0, the real memory is released.

2. does iceoryx has Qos or buffer_queue ?

Contributor guide

Open the contributing guide

Research direction

Start by reading the publisher loan()/publish() flow and the subscriber release() API to establish the current shared-memory ownership semantics. Then check the available QoS and buffer_queue interfaces; done requires a confirmed, documented behavior or a clearly scoped design for reference counting and queue management.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.