Re: Galeon 1.2.5 to 1.3.19 conveersion a couple of questions

On Sun, 2005-02-06 at 16:05 -0800, Karsten M. Self wrote:
> on Sun, Feb 06, 2005 at 11:10:05AM +0000, Crispin Flowerday ([email protected]) wrote:
> > On Sat, 2005-02-05 at 21:19 -0800, Karsten M. Self wrote:
> 
> > >   - Better memory performance.  1.2.x seemed to leak faster than 1.3,
> > >     though 1.3.x is still leaking, and pretty badly at 1.3.19-1.
> > 
> > If anyone can track down these memory leaks, then please tell us, I have
> > tried valgrind, but couldn't see anything major.
> 
> Could you point to some tips for how end-users could do this, and what a
> useful format for a report would be?
> 
> What's the performance impact of valgrind?  Presumably you're running
> Galeon from it, right?

It's easy enough to do: run "valgrind --alignment=8 --num-callers=30
--tool=memcheck --log-file=report --leak-check=yes galeon" (as opposed
to plain ol' "galeon").

The performance impact is unbelievable. You've never seen anything like
it. Next time you go outside, look at your house. Look at how fast your
house is moving, relative to the ground. That speed is about 2.316 times
faster than running a program through Valgrind.

(Okay, I exaggerate, but it's really quite unbearable for normal
day-to-day use.)

-- 
Adam Hooper <[email protected]>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBCBrSL90GtBxQ61zARAh92AKDp2slSb+pDbkCCqxiieJpbSvxj5ACgjybI
QL3biZxQ1AlJEHu66XJgBPw=
=FBGF
-----END PGP SIGNATURE-----