It looks like I’m bumping into threading issues because my internet connections don’t want to time out (win7)…
Now I just bumped into your WORKAROUND_TIMEOUT_BUG define, but haven’t found any references to it anywhere on the forum…
Could you give me some more info?
When should this be defined, when shouldn’t it??
It was a few years ago and I don’t remember all the details, but there was some kind of bug in the win32 internet stuff that I was trying to avoid by making it time-out manually. It was experimental though, I don’t think I left it enabled, but feel free to try it.
[quote=“bdejong”]
I consistently get into stopThread’s “very bad karma if this point is reached” assertion failure…
bram[/quote]
Yeah, I think that I added it as a bit of a emergency fallback way of timing out. There’s probably a better way of cleanly making the win32 stuff time-out, but I never found it. (But MS might even have fixed or updated the APIs since I looked at it)
Found it, it’s not the “connection” that times out, it’s the data sending that times out…
It’s a bit of a mess when it comes to the timeout, but this is a bit of a hacky solution:
It’s a bit of a hack as each of these calls can now take “up to timeOutMs” so in total you would get a possible timeout of timeOutMs*5, but maybe you know a nicer solution to that than me…
It could be solved by ripping the URL getting in two, one for the actual connecting, the second for the sending/getting of data with different timeouts…