.. include:: /../getting_started/vars.rst

.. _section-Regressions710:

Regressions in 7.1.0
********************
The following regressions were introduced in *Connext* 7.1.0.

Core Libraries
==============

Possible unbounded memory growth on DataReader of keyed type after failing to match with a remote DataWriter
------------------------------------------------------------------------------------------------------------
Consider the following scenario:

-  You have a *DataReader* of a keyed type.

-  The *DataReader* discovers a *DataWriter*, but the matching process
   fails somehow (e.g., due to a port collision that generates this
   error: ``assertRemoteWriter:!create entryPort``).

-  The *DataReader* somehow retries the matching process with the same
   *DataWriter* (e.g., due to receiving another discovery announcement
   for the *DataWriter* after the *DataWriter* changes its QoS).

The matching process will fail again and generate this error:

.. code-block:: text

    PRESCstReaderCollator_getRemoteWriterQueue:FAILED TO ASSERT | remote writer queue node in list.

Repeated occurrences of this error message are correlated with an
unbounded memory growth on the *DataReader*.

**Fixed in:** 7.5.0

[RTI Issue ID CORE-15095]


Possible crash when creating DomainParticipants concurrently
------------------------------------------------------------
Creating *DomainParticipants* concurrently can lead to a crash if during the
creation process one of the threads accesses the typecode of the internal
builtin types while another thread is initializing it. 

**Fixed in:** 7.5.0

[RTI Issue ID CORE-14764]

.. _CORE-13968:

Potential bus error when calling print and to_string APIs in TypeCode
---------------------------------------------------------------------
Your application may generate a bus error after calling
the **print** and **to_string** APIs, such as
``DDS_TypeCode_print_IDL``, in TypeCode.
This issue only happens when TypeCode propagation is enabled by
setting
``participant_qos.resource_limits.type_code_max_serialized_length`` to a
value greater than zero (the default is zero) and when using the
affected APIs in the TypeCodes that were part of
``PublicationBuiltinTopicData`` and ``SubscriptionBuiltinTopicData``.

**Fixed in:** 7.3.0

[RTI Issue ID CORE-13968]


Running rtisetenv_<arch>.bat caused issues in PATH environment
--------------------------------------------------------------
Running ``rtisetenv_<arch>.bat`` may cause 
issues in the PATH environment on Windows systems.

**Fixed in:** 7.2.0

[RTI Issue ID INSTALL-880]

Instance purging based on source timestamp does not work
--------------------------------------------------------
The source timestamp-based purge delay does not purge instances
based on their source timestamp. Instead, it purges instances based on
their sequence number. Starting in 7.2.0, the
**dds.data_writer.history.source_timestamp_based_autopurge_instances_delay**
property works as intended.

**Fixed in:** 7.2.0

[RTI Issue ID CORE-13911]


Code Generator
==============

Code not stored in specified output directory on Windows when IDL was in a Symlink
----------------------------------------------------------------------------------
In Windows environments, when generating code using a specified output folder 
for an IDL located in a Symlink folder, the code is stored in the Symlink 
folder instead of the specified output directory. This issue is caused by a 
`JDK bug <https://bugs.openjdk.org/browse/JDK-8003887>`__. RTI has applied a 
workaround in 7.2.0; the generated code is now stored in the ouput directory 
when specified.

**Fixed in:** 7.2.0

[RTI Issue ID CODEGENII-1891]

Command-line option tips not printed if you entered an invalid option
---------------------------------------------------------------------
If you enter an invalid *Code Generator* command-line option, 
*Code Generator* does not print out the helpful list of valid command-line options. 

**Fixed in:** 7.2.0

[RTI Issue ID CODEGENII-1868]

Include flag used without a space caused Code Generator to fail
---------------------------------------------------------------
When using the flag ``-I`` without a space between the flag and the included 
folder, *Code Generator* fails, reporting that the flag is not supported. 
Starting in 7.2.0, you can now successfully use
the flag ``-I`` without a space (for example, ``-I./myInclude/``).

**Fixed in:** 7.2.0

[RTI Issue ID CODEGENII-1867]