[ut2003io] Memory leaks.

[HbG]

Packages.md5 is updated, if not how could the servers possibly be busy? :)

26-9-2002 2:30:04, "Daniel Vogel" <vogel at epicgames.com> wrote:

>Unrelated - please upgrade to 1080c as 1080b won't allow 1080 clients to
>join. (All you need is an updated Packages.md5).
>
>-- Daniel, Epic Games Inc.
>
>> -----Original Message-----
>> From: HbG [mailto:hbg at game2xs.com]
>> Sent: Wednesday, September 25, 2002 4:32 PM
>> To: ut2003 at icculus.org
>> Subject: [ut2003io] Memory leaks.
>>
>>
>> We've been running 1080b linux servers for some time without a
>> reboot now, 9 servers in total on 2 SMP machines.
>> Initially it all ran fine, low pings, no lag, happy players. But
>> after a while i started to notice switching maps was taking awfully long,
>> sometimes over 30 sec. Some players assumed the server crashed
>> and went to another, which is off course every GSP's nightmare.
>> Here's what seems to have caused it:
>>
>>    PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
>>  24738 ut2003    19   0  120M  95M  3688 S    33.6 18.9 505:23 ucc-bin
>>  24726 ut2003    15   0  209M 143M  5912 R    29.1 28.3 458:24 ucc-bin
>>  24748 ut2003    17   0  104M  78M  3644 R    21.2 15.6  1171m ucc-bin
>>  24715 ut2003    14   0  244M 142M  3584 S    11.4 28.1 546:56 ucc-bin
>>
>> With freshly booted servers it looks like this:
>>
>>    PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
>>  15908 ut2003    20   0 70048  68M  5904 R    52.5 13.5   9:39 ucc-bin
>>  15851 ut2003    17   0 73556  71M  5900 S    50.7 14.2  30:05 ucc-bin
>>  15856 ut2003    16   0 74236  72M  6084 R    48.4 14.3  32:00 ucc-bin
>>
>> This didn't seem to happen back with 1077, but that might also be
>> simply because in the first few days the servers were restarted often for
>> testing new settings. They run various gametypes, and get a lot
>> of usage. Tried restarting one with the relaunch command, didn't help.
>> For now as a remedy the servers will be restarted daily in the
>> early hours. Seem's we're dealing with a very nasty bug here. Is
>> anybody else
>> experiencing this?
>>
>> More information available upon request.
>>
>> - HbG
>>
>>
>>
>
>
>