Crossfire Forum

I've been having a really annoying problem. Quite often the client will crash and freeze up as my character is slicing his way through bad guys. If I keep from combat for about 10 minutes, everything seems okay.

Important info:
* I only play localhost with my PC
* I have been playing for about 2 months so my client and server are relatively recent releases. How do I find out?
* Mandrake Linux 10.1 OS
* P3-500, 384mb RAM, 40gb HDD

ALSO:

Sometimes when I'm playing everything slows down. According to my Gnome system monitor I am using upwards of 50mb of Swap. This is annoying because I have 384mb RAM and only about 277 is used. Why can't it use RAM rather than Swap? Is there any way of modifying the server settings for this?

One Salient Oversight wrote: * I have been playing for about 2 months so my client and server are relatively recent releases. How do I find out?

help-> about
for the client

and

crossfire -v
for the server

unless you compiled from CVS in which case you should know anyway.

As for the rest of your problem, I don't know.

Are you playing with sound enabled?

Disable sound (in GTK, client -> configure -> general) and see if that helps.

Ah yes, /me remembers sound - switched it off months ago.

There is some issue with the sound support atm, haven't really paid much attention to the details personally, but the devel-list thread is archived here

http://shadowknight.real-time.com/piper ... 08138.html

you might find it interesting....

slowing down? mmm, some older versions of the client have a memory leak. you likely experience that. (does the memory used by X increase enormously when playing?)

if not, then try to type 'clearinfo on a regular basis. it seems gtk allocates memory dynamically, which cost time and cause the client slowdown when there is a lot of text

Some people have trouble compiling the newer client.
/me curses linux-isms
I use BSD, and sometime I patch the client to build. Others, dont know how to, and may need to build their own client.

i doubt mandrake has your BSD troubles, so he might be able to build his own client

The answer to the swap problem is simple; LEARN HOW MEMORY WORKS.
Also, build SDL image support into the client. That stops the leak.
use a memory management program that allows you to delete the semaphores and unused segments that are in use.

bort wrote:Also, build SDL image support into the client. That stops the leak.

My memory still leaks some with SDL turned on. I can cause the system to run out of memory completely (1GB of swap and 512MB ram) by rapidly inscribing in books with a keybinding till the book is full, then repeating for another few books that there goes all my memory

download cvs and compile. its not that hard

my client only slows down when i get spammed by a lot of 'you kill foo' or 'your pet hits bar'
this is not due to a memory leak, but rather due to gtk's memory allocation

@bort most users are users, not ppl that can spent their lives on learning how their system works