Dave Balmain said: > Running your test for 15 minutes my memory usage climbed to 30Mb. It > was still slowly climbing which is not a good sign but not enough to > bring my system to a halt. Anyway, I tried using valgrind's memcheck > on it and I couldn't find a leak in the Ferret code. Perhaps it is a > leak in your version of Ruby, although I doubt it. Here is the most > significant output from valgrind with --show-reachable=yes set;
Ok, so my ruby is version 1.8.2, kinda old, so maybe there is an old bug in it. Recent experiments on another machine (running a newer ruby, 1.8.5, I think) didn't seem to have the same memory leak. What version do you run, by the way? > Incidentally, I'm not sure what the other bug you are chasing is but > it may have something to do with the encoding of the man pages. I I know the man output is some encoding I don't understand; I'm just trying to generate a lot of data to feed into ferret. I don't care if it's correct. I'm still having quite a few crashes with ferret, though the situation has improved. I'm trying to reproduce those without handing you my entire codebase. So far, without success. :( > don't think they are UTF-8 so if your locale is set to UTF-8 it will > cause some problems in the analysis. I know I'm not on the UTF-8 locale. Actually, I've been trying to figure out how to set my locale to UTF-8. I don't suppose you'd know? I'm using Debian stable. _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
