7.15. Other Known Issues

7.15.1. Possible Valgrind still-reachable leaks when loading dynamic libraries

If you load any dynamic libraries, you may see “still reachable” memory leaks in “dlopen” and “dlclose”. These leaks are a result of a bug in Valgrind (https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1160352).

This issue affects the Core Libraries, Security Plugins, and TLS Support.

[RTI Issue IDs CORE-9941, SEC-1026, and COREPLG-510]

7.15.2. 64-bit discriminator values greater than (2^31-1) or smaller than (-2^31) not supported

Unions with a 64-bit integer discriminator type containing discriminator values that cannot fit in a 32-bit value are not supported when using the following language bindings:

  • C

  • Traditional C++

  • Modern C++

  • C#

  • Java

  • Python

  • DynamicData (regardless of the language)

They are also not supported with ContentFilteredTopics, regardless of the language binding.

Using label values greater than 32-bit may lead to receiving samples with invalid content or to filtering samples incorrectly.

[RTI Issue ID CORE-11437]

7.15.3. Creating multiple DataReaders for the same Topic under the same Subscriber configured with Group Ordered Access is not supported

Creating multiple DataReaders for the same Topic under the same Subscriber configured with PresentationQosPolicy access_scope = GROUP and ordered_access = TRUE is not supported. If you try to create a second reader in this situation, it will fail to be created and this error will be printed:

ERROR [0x0101E967,0x5C3A43B1,0x99D71EB7:0x80000309{Entity=Su,Domain=0}|CREATE DR WITH TOPIC FooTopic|LC:Discovery]PRESPsService_createLocalEndpoint:NOT SUPPORTED | Creating more than one reader for the same topic within a single subscriber using GROUP presentation and ordered_access=true.

Instead, in this situation, you will need to use only one DataReader, or you will need to create a new Subscriber and DataReader in the same DomainParticipant.

[RTI Issue ID CORE-12448]

7.15.4. With DISALLOW_TYPE_COERCION and Types containing unbounded members, other vendor DataWriters/DataReaders will not match Connext DataWriters/DataReaders

When reader_qos.type_consistency.kind is set to DISALLOW_TYPE_COERCION, a Connext DataReader/DataWriter for a type containing unbounded collection members will not match with a DataReader/DataWriter from another vendor.

A possible workaround is to use ALLOW_TYPE_COERCION or disable type validation by not sending TypeObject information.

[RTI Issue ID CORE-14367]