-
Notifications
You must be signed in to change notification settings - Fork 388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Payload size not updated by allocateChunk(WithInfo) #10
Labels
bug
Something isn't working
Comments
Thanks @rex-schilasky. We have an optimization to recycle the last chunk that was sent if this one is free again. As we don't create a new chunk it is not initialized again. So we must check if the old chunk can really be used again and update its payload size |
mossmaurice
added a commit
to mossmaurice/iceoryx
that referenced
this issue
Nov 21, 2019
…hunk and add new tests Signed-off-by: Hoinkis Simon (CC-AD/ESW1) <simon.hoinkis2@de.bosch.com>
mossmaurice
added a commit
to mossmaurice/iceoryx
that referenced
this issue
Nov 21, 2019
Signed-off-by: Hoinkis Simon (CC-AD/ESW1) <simon.hoinkis2@de.bosch.com>
mossmaurice
added a commit
that referenced
this issue
Dec 3, 2019
…nment-when-reusing-last-chunk IOX #10 Fix payloadsize assignment when reusing last chunk
Thank you for fixing that ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Required information
Operating system:
Ubuntu 18.04 LTS
Compiler version:
GCC 7.4.0
Observed result or behaviour:
When allocating a chunk with
allocateChunk
orallocateChunkWithInfo
using the dynamic payload option (useDynamicPayloadSizes = true
) theChunkInfo
fieldm_payloadSize
is initialized correctly by the first call. Subsequent calls of the same function with an increasedpayloadSize
do not update the member variable.Expected result or behaviour:
ChunkInfo::m_payloadSize
should reflect the current payload size under all conditions.Conditions where it occurred / Performed steps:
The text was updated successfully, but these errors were encountered: