Hello Nikita,
On Fri, 7 Oct 2005 17:48:23 +0400 Nikita Bige <[EMAIL PROTECTED]> wrote: > > I've never seen Licq use that much! How long have you been running > > Licq? I've had it up for weeks and it didn't exceed 30MB. There may be > > some memory leaks, I was planning on running it against valgrind soon, > > just to check. > Eh.... about 47minutes ... > I think the problem in reading the _whole_ history files. > Every time when the new window pops up (according to programm top) utilized > memory increase by ~6mb. > How I can help to find the problem? Telling us what plugin(s) you use. Running licq from valgrind for as long as you can (hours?) in order to get a log that will show memleaks and other potential problems. From valgrind, licq will run be much slower and might even be hardly use-able, but it is important to use it as you usually use it (to reproduce the same running conditions). For instance: valgrind --num-callers=8 --trace-children=yes --tool=memcheck --leak-check=yes --show-reachable=yes --leak-resolution=high -v licq >licq-memcheck.txt 2>&1 Regards, -- wwp ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Licq-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-devel
