Access violation crypt32.pdb in Titanium.Web.Proxy.Examples.Wpf

[dicehira]

Using ver. 3.0.481 or 3.0.503, access violation of crypt32.pdb occurs in the example code (Example.Wpf).
When the application is built, no error occurs. But scanning network in a few minutes, this error occurs.
I want to know the way to work around this error in latest version.

[justcoding121]

Did you try latest beta?

Install-Package Titanium.Web.Proxy -Version 3.0.623-beta

[dicehira]

Thank you for your response. Same error occurs in latest bata.
My environment is Windows10 (64bit) updated from Windows7.

[nerodark]

I am also getting this error when in my BeforeResponse event handler.
It gives an access violation of crypt32 after a certain amount of time or after intensive use of getting body line code:
string body = await e.GetResponseBodyAsString();

when I comment it, I can let the proxy server on for days without problem.

[justcoding121]

Is this a fatal error. Does it shutdown the proxy?

[nerodark]

Yes the whole EXE crashes

[justcoding121]

couple of more questions.

• Did anyone try switching the certificate engine and see this still happens.
• Happens only on .net 4.5 or in .Net core. What is the operating system.
• pdb files are usually in debug mode, if so does this happen in release mode too.

I am not sure on the cause and still looking to it. But this link may have some details for possible resolution.
https://support.microsoft.com/en-au/help/982416/an-application-that-uses-crypt32-dll-crashes-on-a-computer-that-is-run

[nerodark]

It happened also in Release mode.
I also enabled this line of code because you were talking about certificate engine:
proxyServer.CertificateManager.CertificateEngine = Network.CertificateEngine.BouncyCastle;

and it seems to not happen anymore, at least not for the last 36 hours straight with heavy traffic. I used to reproduce it every 5 minutes. I have been testing it intensively. I am on windows 10.

I think this line of code is a good workaround for now :)

[justcoding121]

Would appreciate if someone can find the cause of this error and suggest the fix.

[danucalovj]

I had a similar issue with awaiting for responses and hanging the process, didn't get deep enough to see if it was related to certificate engine issues, but I created an if statement to check first if content length was greater than 0 and no further crashes observed. Mine was on Winforms.

[honfika]

Can you reproduce the issue with the latest beta package?

[honfika]

I close this isse, feel free to reopen if needed.