8.3. What’s Fixed in 2.4.14.3¶
The following are fixes since 2.4.14.2.
[Critical]: System-stopping issue, such as a crash or data loss.
[Major]: Significant issue with no easy workaround.
[Minor]: Issue that usually has a workaround.
[Trivial]: Small issue, such as a typo in a log.
- 8.3.1. Discovery
- 8.3.1.1. [Critical] Lost INFO_DST messages with GUIDPREFIX_UNKNOWN
- 8.3.1.2. [Critical] Failure to interoperate with other DDS implementations if default multicast locator was specified
- 8.3.1.3. [Major] Possible mismatched endpoint messages during discovery
- 8.3.1.4. [Major] DomainParticipants continued to send DATA(p) messages to nonexistent remote participants
- 8.3.1.5. [Minor] Participants using DPDE sent one extra announcement message
- 8.3.2. Reliability Protocol and Wire Representation
- 8.3.3. APIs (C or Traditional C++)
- 8.3.4. Crashes
- 8.3.4.1. [Critical] NULL pointer access in AUTOSAR Classic when a ping message received from Connext Professional 7.3.0 or higher
- 8.3.4.2. [Major] UDP transport may have caused a segmentation fault on LynxOS systems
- 8.3.4.3. [Major] DDS_DomainParticipantFactory_delete_participant was not thread-safe
- 8.3.5. Hangs
- 8.3.6. Memory Leaks/Growth
- 8.3.7. Platform and Build Changes
- 8.3.8. Interoperability
- 8.3.9. Other
- 8.3.9.1. [Critical] No communication on AUTOSAR systems with multiple IP addresses
- 8.3.9.2. [Major] Samples with meta-information were not delivered to the user if they arrived when history cache was full
- 8.3.9.3. [Major] DataWriter with finite timestamp failed to send data if date exceeded January 2038
- 8.3.9.4. [Major] Connext Micro would not work if year exceeded 2038