Access Violation in the libema thread

dmitry.kozhevnikov

what should we do about it?

loggerMsg
TimeStamp: 16:01:03.630
ClientName: OmmConsumer_2
Severity: Error
Text: EMA Exception Handler
Application: ec_jnt1_connector_reuters
Process Id: 0x274C
Thread Id: 0x29A8
File: \Jenkins\workspace\ESDKCore_RCDEV\OS\VS150-64\rcdev\source\esdk\Cpp-C\Ema\Src\Access\Impl\Thread.cpp
Line: 43
Exception "Access Violation" (0xC0000005) occured at 0x00007FFACF732F15: memory at 0xFFFFFFFFFFFFFFFF cannot be written
Stack Trace:
0x00007FFACF732F15 \ECN-Core_JNT1\bin\connector_reuters\librsslVA.dll: rsslTunnelStreamRequestGetCos() + 96245 bytes
0x00007FFACF7332FB \ECN-Core_JNT1\bin\connector_reuters\librsslVA.dll: rsslTunnelStreamRequestGetCos() + 97243 bytes
0x00007FFACF732D0B \ECN-Core_JNT1\bin\connector_reuters\librsslVA.dll: rsslTunnelStreamRequestGetCos() + 95723 bytes
0x00007FFACF72A2EF \ECN-Core_JNT1\bin\connector_reuters\librsslVA.dll: rsslTunnelStreamRequestGetCos() + 60367 bytes
0x00007FFACF728021 \ECN-Core_JNT1\bin\connector_reuters\librsslVA.dll: rsslTunnelStreamRequestGetCos() + 51457 bytes
0x00007FFACF748533 \ECN-Core_JNT1\bin\connector_reuters\librsslVA.dll: rsslReactorCloseChannel() + 9955 bytes
0x00007FFACF744A29 \ECN-Core_JNT1\bin\connector_reuters\librsslVA.dll: rsslReactorDispatch() + 889 bytes
0x00007FFACFF1E69E \ECN-Core_JNT1\bin\connector_reuters\libema.dll: thomsonreuters::ema::access::OmmAscii::hasEncoder() + 45118 bytes
0x00007FFACFF1FA4C \ECN-Core_JNT1\bin\connector_reuters\libema.dll: thomsonreuters::ema::access::OmmAscii::hasEncoder() + 50156 bytes
0x00007FFACFF8B9AF \ECN-Core_JNT1\bin\connector_reuters\libema.dll: thomsonreuters::ema::access::SummaryData::getAnsiPage() + 319 bytes
0x00007FFADB91F4A0 C:\Windows\SYSTEM32\ucrtbase.DLL: o__realloc_base() + 96 bytes
0x00007FFAE3E913F2 C:\Windows\system32\KERNEL32.DLL: BaseThreadInitThunk() + 34 bytes
0x00007FFAE44154F4 C:\Windows\SYSTEM32\ntdll.dll: RtlUserThreadStart() + 52 bytes
loggerMsgEnd

nick.zincone

Hi @dmitry.kozhevnikov,

Access violations are typically unpredictable and can occur anywhere within your application and show up in unsuspecting libraries. If you believe it is an issue within the EMA libraries that you can easily reproduce, what you should do is package up a small code snippet and report it as an issue. In addition, share your code snippet here and how to reproduce so we can try to verify.

Thanks.