shame, I still can't get it to crash been hammering for a few hours now. My Steamcast log is now 70MB. Maybe it's a Win2k thing. Do you have all the latest patches for your system?

I'll reuplaod what I have at www.steamcast.com/downloads/steamcast/steamcast.exe

When you get a chance try it out and ...

ok with all logging capabilities enabled a wrote a utility to hammer the server (faster then a script) it's connecting at an astonishing 115 connections per second and still no crashing.

I'll let it go for a bit though. At least I think we might finally be getting somewhere. If I still get stumped ...

Ok let me know if it does crash or not. Then I can at least pin point where the problem may be.

try disabling both screen log and file logging and see if it crashes.

Something else you might try is just hammering with no source connected and see if that makes any difference. That will help me determine better where to look next.

well I just setup a script to hammer the local server right now I am getting about 40 connections per second.

strange, I have 12 winamps hammering the shit out of it and it doesn't crash.

I guess I need to write something to hammer it more effectively then this. Perhaps my machine is too slow to really get the full effect. 2.8Ghz CPU

do me a favor and try out www.steamcast.com/downloads/steamcast/steamcast.exe

Let me know if it continues to give you problems, appearently vsprintf is not thread safe :p

I was able to reproduce. Looks like the logging code get's quite messy if the server is being hammered relentlessly.

are you using winamp?

I will try to see if I cannot setup something to hammer my local server here and see if I can reproduce.

I have had another report of issues on SP2 so getting a fix out will just be a matter of me getting a hold of XP SP2 and installing it on a spare machine.

If you have a question you do not want to ask in public you can private message me through this forum board. Click the "PM" image below this ...

ok I will see if I can't get a hold of a SP2 box and test it out.

Just for clarification this is the source doing this correct? If so just use your internal IP.

works in WMP for me.

works like a charm

My ip is 24.0. something or another, can't remember off hand.

You can pretty much assume that broken pipe and connection resets are committed by the client. Basically they stopped listening.