.:: Bots United ::. - View Single Post - Non-Steam v19+ closes and quites into OS.

vityan · **Non-Steam v19+ closes and quites into OS. -** 02-09-2005

[Whistler]
You wrote very good bots.
Nice AI and relatively(at least to [e]pod and pod-mm) clean code.

But where is some big trouble.
When playing with bots under non-steam v19+(v19,v20,v21,v22) after playing some time(maybe 2 hours,10 minutes,hour) game quit's to operating system without any error/warning message.
Tested BOTH with GF2 and Radeon 9250 graphic cards so i sure it's not drivers problem.Memory has been tested with memtest86(linux) for 4 hours without errors...
And the most importand fact is where is NO this problem whith non-steam v17/v18.
It's maybe protocol interaction problem(buffer overflow or another mem leak) cause after each quit to OS Steam*.mdmp process memory dump file appears in CS installation dir.I not diagnosed dump files cause i not acquainted with structure of Steam protocol.

Tested on Win2kSP2/Win2k3 SP1 With 2 different Video Cards and multiple driver versions/different heapsize parameter values/Different bot_quotas(8-20) and different RAM size(256/320/512) and Swap sizes.
Heap parameters in registry set to automatic allocation by OS.

I'll hope you can check this problem out and hopefully fix that.
This BUG exists only when bots loaded.
When i'm alone or playing on net/inet where's no problems.

	(#1)
vityan Member Status: Offline Posts: 5 Join Date: Jul 2005	Non-Steam v19+ closes and quites into OS. - 02-09-2005 [Whistler] You wrote very good bots. Nice AI and relatively(at least to [e]pod and pod-mm) clean code. But where is some big trouble. When playing with bots under non-steam v19+(v19,v20,v21,v22) after playing some time(maybe 2 hours,10 minutes,hour) game quit's to operating system without any error/warning message. Tested BOTH with GF2 and Radeon 9250 graphic cards so i sure it's not drivers problem.Memory has been tested with memtest86(linux) for 4 hours without errors... And the most importand fact is where is NO this problem whith non-steam v17/v18. It's maybe protocol interaction problem(buffer overflow or another mem leak) cause after each quit to OS Steam*.mdmp process memory dump file appears in CS installation dir.I not diagnosed dump files cause i not acquainted with structure of Steam protocol. Tested on Win2kSP2/Win2k3 SP1 With 2 different Video Cards and multiple driver versions/different heapsize parameter values/Different bot_quotas(8-20) and different RAM size(256/320/512) and Swap sizes. Heap parameters in registry set to automatic allocation by OS. I'll hope you can check this problem out and hopefully fix that. This BUG exists only when bots loaded. When i'm alone or playing on net/inet where's no problems.