EMA OmmConsumer memory leak in C++ API?

Hi Umer,

When I'm following your Premium Support Ticket link I'm getting

Something Went Wrong
We were unable to retrieve the page you were trying to reach. We don't want to leave you hanging though.
Go back or see other APIs you may be interested in...

Thanks.

Hi @dmitry.kozhevnikov

This would be the case if you are not a named user for your organisation or if your organisation does not have a RDC support membership.

You can check with your Market Data team or your Refinitiv account manager to find out if you do have a named member who can raise a Premium support ticket on your behalf.

In terms of the other Java post, it appears the user opened a Support ticket and closed the ticket after receiving guidance from the RDC team.

If your organisation does not have a Support membership, then you can report your issue on Github and it will be looked at as a best endeavours basis by the support team.

Also, did you try to use the ChannelSets as mentioned above - as this would is the recommended way i.e. letting EMA deal with connectivity issues and failover scenarios - rather than doing it at an application level.

I do experience the memory leak as well.

Due to some reasons (not important why) I need to dispose (uninitialize) the OmmConsumer and create a new instance of OmmConsumer. However after roughly 27 iterations (destroy OmmConsumer and create new one) the process consumes 16 GB of memory and crashes. Worth mentioning that this happens even if no clients are registered.

The ChannelSet feature is not what I am looking for and it won't help me.

Thank you, I have submitted the issue to GitHub.

This issue has been reported on GitHub
https://github.com/Refinitiv/Elektron-SDK/issues/118
JIRA ID: ESDK-3495

Based on the latest post from the issue, the development team is working on this issue, and it will be fixed in the next release.

You can change EMA default behavior to log the EMA messages to Stdout as the workaround. We can put EmaConfig.xml to a running directory and then change LoggerType in configuration file to Stdout instead.

DefaultConsumer in the XML file is Consumer_1 and it use Logger_1 therefore we need to change LoggerType in Logger_1 section to LoggerType::Stdout.

<DefaultConsumer value="Consumer_1"/>

<ConsumerList>

<Consumer>

<Name value="Consumer_1"/>

<Channel value="Channel_1"/>

<Logger value="Logger_1"/>

<Dictionary value="Dictionary_1"/>

</Consumer>

…

<Logger>

<Name value="Logger_1"/>

<LoggerType value="LoggerType::Stdout"/>

<LoggerSeverity value="LoggerSeverity:: NoLogMsg"/>

</Logger>