Closed GalaxyDreamWings closed 1 month ago
Hi @GalaxyDreamWings, thanks for using Fast DDS.
We will have a look and try to reproduce the issue. We will come back with a feedback.
Hi @GalaxyDreamWings
I have been testing with the following diff using a modified version of the ContentFilterTopicExample
with the information you provided but I could not reproduce the issue. With that patch applied I tried DDSContentFilteredTopicExample --publisher
in one terminal and DDSContentFilteredTopicExample --subscriber
in another, then killing and relaunching the publisher several times, but no crash occurred.
I'm afraid that we would need more information about the application or a reproducer from your side, would it be possible ?
Hi!@Mario-DL Thanks for your reply! But I'm sorry that I can't put my code here for some reason. I run my application in docker container on aarch64 server, so have you tried it? And It is confusing that it won't always crash, instead, it will run normally for a while , and crash occasionally. Also, the coredump trace always stop at eprosima::fastdds::dds::ContentFilterInfo::cdr_serialize function, but the data to be written seems normal. So can you find some clues for the problem with the coredump info that I provided? I can't solve it so I have to turn to try PartitionQos to achieve filter functionality. Hopes for your reply!
Hi @GalaxyDreamWings,
Sorry for the delay in the response. Im afraid that we would need at least a simple reproducer to double check this. A hard guess would be that we are exceeding the num_filters
, or not enough space in the SerializedPayload_t
. In addition the platform goes out of the scope of supported platforms. I am moving this ticket to the appropriate forum.
Is there an already existing issue for this?
Expected behavior
use ContentFilteredTopic and set filter expression to receive required data
Current behavior
The operation seem to be valid and the application can run normally for a while but would crash occasionally or even frequently with segment fault. But if DataReader doesn't use ContentFilteredTopic, everything is well. The call stack is shown below:
Steps to reproduce
The IDL file:
And the filter expression:
relevant code for write data:
Fast DDS version/commit
2.14.x
Platform/Architecture
Ubuntu Focal 20.04 arm64, Other. Please specify in Additional context section.
Transport layer
Default configuration, UDPv4 & SHM
Additional context
Galaxy Kylin OS (Linux) aarch64 run in docker
XML configuration file
No response
Relevant log output
No response
Network traffic capture
No response