On Tue, Jul 09, 2002 at 12:51:01AM -0500, David Fries wrote: > Speaking of memory usage, has anyone thought about looking for some > memory leaks?
Yes, we regularly run Purify or a similar tool before major releases. In the mean time I frequently use efence to detect other memory problems. > Ok so I've been a lazy Debian user and I'm not up to > what's in CVS (2.4.7 right now), but here's what I'm seeing (from top). > > PID USER PRI NI SIZE SWAP RSS SHARE STAT %CPU %MEM TIME COMMAND > 668 david 8 0 15300 8948 6352 3440 S 0.0 1.9 3:35 fvwm2 > after restarting fvwm, same windows etc > 668 david 10 0 2468 0 2468 1348 S 0.1 0.7 3:36 fvwm2 > > Let's see, 15MB vs 2.4MB, could be. It could also be fixed by now in > CVS. Unfortunately, the information about memory usage that top shows has little to do with the real memory consumtion. Chances are good that you didn't see a memory leak at all. > Does anyone have a favorite memory leak checker? My favourite is insure++, but the company totally freaked out: they demand about EUR 10000 for a single, CPU locked license. Since we couldn't convince them to sponsor a license for our work, we usually run Purify - which is vastly inferior to insure++ - but we have a few people on the list who can run it. > I've tried two, but > I haven't been to impressed with them. One was called memusage (at > least on SuSE), and said what was allocated/freed and sizes but I had > no idea where the leak was, or glibc doing exit instead of free..exit. Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
