Mopping Up Mozilla Memory Leaks
mouseman writes "Geodesic Systems, a maker of memory management/debugging software, has a live demo of their Linux product running on the Mozilla nightly builds. It's pretty damn slick -- it detects memory leaks and can show where in the code the leaked memory was allocated and actually recover (GC) the leaked memory. The Mozilla reports actually look pretty good, which jibes with my own impressions of how much it has improved -- see for yourself."
It's really improved a lot. 0.97 was painfully slow on OS X, but 0.99 is actually faster than MSIE. There are still a few UI glitches - for example, command-H doesn't work - but this is the first time I've been able to switch to Mozilla and not have to switch back within an hour. I'm still going strong after three days. Things are definitely looking up for Mozilla.
Tabbed browsing is far better than anything IE has.
and, guess what, your pressiouse Mem foot print, well I looked at my memory used before I IERadicated my IE, after ward, I gained a ton of memory with out IE on my system.
IEs memory foot print is hiden from you, that is why it takes windows so long to load, because IE is in memory at boot.
I am the Alpha and the Omega-3
oh yeh... that will definitely help when you've got a memory leak the size of ontario from a program that stopped executing an hour ago.
or, you've got a pointer that went off its bounds and started writing all over its instructions, and the program crahes 1000 lines after the viiolation....
sometimes, printf, jsut isnt enough.
... hi bingo