Support Board

Date/Time: Thu, 02 May 2024 13:35:14 +0000

Post From: Caught an unhandled exception in AsyncWindowProc for ACSIL Study

[2015-11-22 03:51:58] Link To Thread - Link To Post [Go To First Post]
Jayturn - Posts: 15
Thank you for the response Sierra Chart Engineering. You are most likely correct about memory corruption being the issue, though it's related to my introduction of the log4cplus library to manage various facets of my custom study logging. If I disable my object interface, forming a connection between the ACSIL Study and the Log4Cplus DLL, the error doesn't occur. The reason I asked you for more details around error message 1025 and the parameters provided is so I can get an idea of what is breaking. I know you guys won't help me debug an issue with the level of custom development I am going to, however right now the only thing I have to go on is an ambiguous error message (Message: 1025) that doesn't help me. Can you please at least provide me with the description of the message 1025 and what wParam and iParam points to?