6.4.3. Fixes Related to Debuggability
6.4.3.1. [Critical] Hang/crash when invoking a DataReader/DataWriter discovery snapshot within a callback function *
A hang or even a crash occurred when trying to get a discovery snapshot from a DataReader or DataWriter within a callback. RTI strongly recommends avoiding calling discovery snapshot APIs in callback functions in release 7.0.0. This issue has been fixed in 7.1.0.
[RTI Issue ID CORE-12959]
6.4.3.2. [Major] Unexpected fatal error when number of instances reached the limit *
In 7.0.0, an unexpected fatal error could be logged when the following occurred:
A DataWriter is configured to use durable writer history.
The number of instances reached the max_instances limit set in the DataWriter’s RESOURCE_LIMITS QoS.
Connext could not find an instance to delete (such as an unregistered one), to replace with the new instance. So the new instance could not be added.
This log message is expected, but it is not a fatal error, so its verbosity has been updated to WARNING, as follows:
WriterHistoryOdbcPlugin_createResources:FIND FAILURE | Instance for replacement
WriterHistoryOdbcPlugin_addInstance:OUT OF RESOURCES | Exceeded the number of instances. Current registered instances (128), maximum number of instances (128)(writer_qos.resource_limits.max_instances)
[RTI Issue ID CORE-13496]
6.4.3.3. [Trivial] Memory leak if network capture initialization failed
Failure to initialize network capture for a DomainParticipant may have caused a memory leak of 746 kB. The leak only happened (upon DomainParticipant creation) if the initialization failed when creating the status mutex for a manager:
!create status mutex for the network capture manager
This issue is now fixed. A failure creating the status mutex for a manager does not leak memory anymore.
[RTI Issue ID CORE-13018]
6.4.3.4. [Trivial] Unexpected log messages at warning verbosity
You may have seen the following unexpected log messages at the warning verbosity level:
!get xxx remoteWriter
!get xxx remoteReader
!goto WR xxx remote reader
!goto WR xxx remote writer
These warnings did not signal any unexpected scenario, and they have been removed.
[RTI Issue ID CORE-13434]
* This bug does not affect you if you are upgrading from 6.1.x or earlier.