On Thu, Feb 15, 2007 at 11:11:14PM +0200, Donn wrote:
One thing that was mentioned to me in the many threads I've started on ubuntuforums.org to try and solve the problem is that performance degradation over time (during the same session) can sometimes be attributed to a memory leak.
How would I trap a memory leak? Is there some kind of logging software I can run that will decide this issue? Bryce has given me a list of things to try, but perhaps there's something more specific to memory leaks.
'top' will reveal this - I don't remember if I mentioned memory leak explicitly, but that's exactly what my first suggestion is aimed at determining. Run top and look at the memory %'s of apps over time. If one keeps growing and growing, then a memory leak is likely.
If you want a more hard core way of investigating memory leaks, 'valgrind' is a good tool for that. However, it may take a while to learn how to use it properly. (It'd be great to see more people using valgrind against Inkscape in general.)
No. Really. I have had this same machine for about +-8 years. The m/b is about 3 now cos lightning had a talk to the last one. It's the same CPU. 512K of my RAM is about the same age, the rest is about 1 or 2 years old. This same machine with the same IDE cables has run everything from Win 2000 and XP to Fedora 1, Fedora 3 and Ubuntu Hoary and now Kubuntu Dapper.
Mismatched memory can also be a culprit sometimes; try taking out the older memory chip(s) and running with less memory, and see if that makes the system work fast.
Bryce