Disable Fast DDS shared memory transport on Windows - #562
Open
mjcarroll wants to merge 1 commit into
Open
Conversation
Opening a shared memory segment left inconsistent by an abruptly terminated peer faults inside SharedMemGlobal::open_port_internal, killing the test process with an access violation. Signed-off-by: Michael Carroll <mjcarroll.oss@gmail.com>
|
Tick the box to add this pull request to the merge queue (same as
|
Member
Author
|
Windows: |
|
Just noting here that someone also made a PR with a similar fix but for system_test (which I think was also hitting the same issues) |
Member
Author
|
I have filed an issue upstream (and will have a PR shortly) to make shared memory handling a little safer in this scenario: eProsima/Fast-DDS#6501 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Opening a shared memory segment left inconsistent by an abruptly terminated peer faults inside
SharedMemGlobal::open_port_internal, killing the test process with an access violation (0xC0000005).check_sanity()walks the allocator red-black tree through pointers stored in the segment. The fault is not a C++ exception, so the surroundingcatch (std::exception&)does not intercept it.Workaround for #539; root cause is upstream in Fast DDS.
Yes I used AI, and it hates using the pull request template