10. Release Notes

• 10.1. Supported Platforms and Programming Languages
• 10.2. What’s New in 2.4.16
  • 10.2.1. Deprecations and Removals
• 10.3. What’s Fixed in 2.4.16
  • 10.3.1. Discovery
  • 10.3.2. Reliability Protocol and Wire Representation
  • 10.3.3. Generated Code (C)
  • 10.3.4. APIs (C)
  • 10.3.5. Memory Leaks/Growth
  • 10.3.6. Data Corruption
  • 10.3.7. Interoperability
  • 10.3.8. Other
• 10.4. Previous Releases
  • 10.4.1. What’s New in 2.4.15
  • 10.4.2. What’s Fixed in 2.4.15
  • 10.4.3. What’s New in 2.4.12.1
  • 10.4.4. What’s Fixed in 2.4.12.1
• 10.5. Known Issues
  • 10.5.1. Network interfaces cannot have non-ASCII characters in their name
  • 10.5.2. Script errors when running from a directory with a space in its name
  • 10.5.3. Low resolution timestamps may cause Zero Copy samples to remain visible longer than expected
  • 10.5.4. DDS_WstringSeq instance may have inconsistent state when set_maximum fails
  • 10.5.5. Logging mechanism is not included by default
  • 10.5.6. DDS_DomainParticipantFactory_get_instance() not memory safe on some architectures
  • 10.5.7. Samples cannot be reclaimed if Zero Copy application does not return loan
  • 10.5.8. VOLATILE Zero Copy DataReaders behave as TRANSIENT_LOCAL
  • 10.5.9. Reliable DataWriters send Heartbeats to best-effort DataReaders
  • 10.5.10. Static endpoint discovery requires unique object IDs across all remote endpoints