For what it’s worth, I’m seeing lots of new Stack overflow exceptions with R4, though unrelated to Xojo.Net.HTTPSocket. At least probably unrelated. It does happen at app startup, which also does an update check. But the stack trace doesn’t mention the socket. For example, here’s the full trace of one such exception:
None of my own code in the trace. It’s not consistent, and R3 doesn’t do it either. My point is I think something isn’t quite right with R4. I’ll be skipping this release, which is unfortunate because I was intending to give URLConnection some real-world usage and get reports filed so it can get some polish for the next release.