ERACC wrote: > > Otherwise if some kind soul(s) would please offer assistance I would > be eternally grateful. :-) Perhaps a suggestion of which libraries > and versions of same I *should* be using would help. Someone with a > successful, non-memory-leaking, GTK+ 1.6.0 CVS client build on Linux > should be using the libraries about which I need to know. I've not noticed any horrendous memory leaks on my system. But I'm using gtk 1.2.10, gcc 3.2.3. However, there are also lots of options that one can use with the client, and certainly possible that one causes more memory leakage than another. For example, I typically use image caching adn sdl display mode. non caching or non sdl may make a difference. But even there, the entire image set can't possible take more than 60 MB or so of memory (yes, that is a lot, but I'm assuming worse case scenario - 4 bits per pixel, and different image sizes for the icons vs map, as well as the pre rendered fog of war spaces (eg, one image may have 3-4 different renderings). OTOH, if you really want to track this down, you can get a leak detector. I see that rational purify has free demo version for linux now (go to www.rational.com as a starting point). Purify tends to be very good about finding lost references and whatnot, and will also find leaks in libraries, and its quite easy to use. I'm a little frightened at how many leaks it may find :) _______________________________________________ crossfire-devel mailing list crossfire-devel at lists.real-time.com https://mailman.real-time.com/mailman/listinfo/crossfire-devel