The issue can be reproduced by running the OTL example StringListParser application in 64bit. For me it crashes on startup with
Project StringListParser.exe raised exception class $C0000005 with message 'c0000005 ACCESS_VIOLATION'.
Breaking at the exception puts you in the TOmniTaskExecutor.GetMethodAddrAndSignature procedure at the folowing place:
// Loop over the parameters
while (cardinal(params) < headerEnd) do begin
{$IFDEF OTL_KnowsParamCount}
-> if paramNum >= returnInfo.ParamCount then
break; //while
I hit that in my own applications that create similar background workers. Let me know if I can supply any more info.
The issue can be reproduced by running the OTL example StringListParser application in 64bit. For me it crashes on startup with
Project StringListParser.exe raised exception class $C0000005 with message 'c0000005 ACCESS_VIOLATION'.
Breaking at the exception puts you in the TOmniTaskExecutor.GetMethodAddrAndSignature procedure at the folowing place:
// Loop over the parameters
while (cardinal(params) < headerEnd) do begin
{$IFDEF OTL_KnowsParamCount}
-> if paramNum >= returnInfo.ParamCount then
break; //while
I hit that in my own applications that create similar background workers. Let me know if I can supply any more info.