This project is read-only.

Deadlock during jit compilation and logging

May 13, 2014 at 1:19 PM

I just want to point out about the problem which I had. Actually I was going to discuss about turning off the logging/tracing in LibZ/AssemblyResolve event, but fortunately in the meantime it has already done.

I have described the deadlock problem here:

Now I see that the latest version of LZ4NET is built using LibZ v which has already turned the problematic tracing off and it is configurable using windows registry settings.