Exception in InoSim using logged PMC

[michelpons]

When an instance of a property package manager is created on a logged PPM, an exception occurs with InoSim as a PME.

EXCEPTION_ACCESS_VIOLATION in module log4cxx.dll at 0023:083C42D3, log4cxx::Logger::info()+0003 byte(s)

[michelpons]

Communication from InoSim developer: \"I used the latest version of COLTT from SourceForge. Unfortunately, no log file is created. But I attached the stack trace (Exception1.txt) for the first chance exception and (Exception2.txt) the second chance exception. As you can see in the file Exception2.txt, the crash occurs in the CoCreateInstance call that creates an instance of the property package. I hope this helps.

It looks to me that creating any CAPE-OPEN object (V1.1 property package, V1.0 thermo system, ...) result in crash, when logging is enabled. \"

[michelpons]

Stack trace first chance exception

[michelpons]

Stack trace 2nd chance exception

[michaelhalloran]

Is it possible to get a copy of Inosim so that I can attempt to reproduce this?

[michelpons]

See bug#161: it does not seem to me that the issue is directly related to INOSIM. I have encountered a similar issue with COFE while using a well known PP. may be related to the operating system. INOSIM does not work under Windows XP but under Vista or Win 7. Bug #161 is observed under Win 7.

[michelpons]

A crash is confirmed when using COLTT 2.1 official release, aka Build 239. When logging is enabled on the Thermo System that one wants to select with INOSIM, expanding the list of Property Packages managed by the Thermo System leads to a crash from InoSim. No COLTT log has been found of what is going on.

[michaelhalloran]

TRAC #161 was caused by interface changes for controlling error logging and Reference counting; the change was not present in the official 239 build at the 2.1 release so I think 161 and this issue are unrelated.