rljonesau

Just to touch on this, I have also narrowed down crashes on my system to also be related to calling publish. There is a similarity too in that new(unsigned int)...

I have been having the same problem with exceptions, especially related to poor signal quality. I'm only using HTTP, but what I have tried instead of commenting out the closeConnection()...

As way of my usage explanation, I have a couple of special paths for special functions that initiate a form POST in return, so an initial GET of the path...

Likewise I'm experiencing stack overflow generating both 2048 bit & 1024bit keys. 1024bit key crashes much more quickly than 2048, which suggests an issue towards the end of the process?

If you pull the source code, then edit line 1436 of MainForm.cs to become: **` resultTextSource += String.Format("\t{{{0}{1}{2}}}, \t\t{3}'{4}'{5}" + nl, `** The comment will then be produced like this:...