Error in C# binding - Attempted to Read or Write Protected Memory about leopard

[laves]

Hi @kalengi, thank you for your detailed report. One question: does your server handle the requests asynchronously? I see you are using a single instance of Leopard to process all server calls. If a call to ProcessFile is made and then another before the first finishes, I would expect there to be an issue. If this is a possible situation, I'd recommend having one Leopard instance per request or a pool of pre-initialized Leopards to handle requests without conflicting. If this is not the case, we can look into your idea that it may be caused by conflicting dll architectures.

[kalengi]

Hi @laves,

Thanks very much for these insights. The Server requests are indeed asynchronous, and your solution may sort out the memory access issue.

I shall implement the Leopard pool and report back on the result.

[kalengi]

I can confirm that implementing a Leopard Pool eliminated the AccessViolationException.

[laves]

Great!