World Firefox Day
kbrosnan writes "Are you a fan of Firefox? Want to spread the word to a friend who hasn't heard of it yet? If you can convince just one person to switch to Firefox before September 15th, you'll both be immortalized in Firefox 2.0's source code."
> Hell yea. My idea of celebrating worldfirefox day is getting the HUGE memory leak squashed.
It's not a leak it it's intentional - it's simply huge memory usage.
From the FAQ: How will our names be included in Firefox 2? If both you and your friend opt-in to have your names included, we'll add your names to an interactive Firefox friends display that will be accessible from within Firefox 2.
--vrwarp
There's no mention at all on the world Firefox day website that the names will be listed in the source. From what I can see this'll just be a link to a site that lists the names (probably accessible from the 'about' box). So there'll be no bloat to the source, not even as a comment.
OK I don't like IE but literally to open slashdot then click on this story Firefox is using 66260k. So Just out of curiosity I opened IE. and open the same exact pages leading back to this slashdot story. 35628k WHY? Really why. Oh and uh why every few seconds does the firefox amount increase and IE stays the same?? Really this is not a troll or a flame thing. I just want to know why my IE with google and yahoo toolbars uses less memory then Firefox by near double? Oh and firefox is now using 65964k with out doing anything but displaying the page. REally HELP.
OMG Ponies!!! with Glitter!!!! I miss Pink
I assume that all the names would be inserted into the code as comments, meaning the names won't be compiled into the binary. I'm not a cvs master or anything but I assume you can exclude the directory that contains the names when you update your source locally.
If your user account has higher-than-user privileges you can combine this with SysInternals' PsExec to launch Firefox Preloader with limited permissions -- this ensures ensures Firefox will always run with low privs even if it's opened via a hyperlink from another program:
(I first saw this tip in a blog comment on SysInternals site regarding PsExec and have used it ever since)
One way to reduce start-up times is to always keep it in memory using Firefox Quickstarter:
http://mozillaqs.sourceforge.net/
This chap built quickstarters for both Mozilla & Firefox. Doesn't addres the huge RAM usage, but it does effectively 'speed-up' starting the frontend (which does seem to have a tiny memory footprint, the main footprint is in the runtime environment itself...)
l'Homme n'est Rien l'Oeuvre Tout: Gustave Flaubert to George Sand