Windows Low Fragmentation Heap builds

As promised, some Minefield beta 1 Windows builds with the low fragmentation heap turned on.


These are built off of the beta1 branch. Beta 1 isn’t out so this isn’t final use at your own risk blah blah blah.

I am curious to hear how these compare memory use wise to other builds for people.

I’m working on putting together an extension (maybe updating RAMBack) to let you produce pretty heap images but I’m not there yet. Stay tuned for that.

7 thoughts on “Windows Low Fragmentation Heap builds

  1. Pete Kruckenberg

    I’ve been using this build all morning, and even pushed hard it stays around 130-150MB RAM (after starting at ~40MB). Closing pages even decreases memory use!

    I haven’t been able to test Firebug, which I’m sure drives up memory use in normal Firefox builds. Firebug 1.1 beta works with 3.0a8, but I can’t get it to activate in this build.


  2. pavlov Post author

    Thanks for the results! I’ve got my binary component for heap dumping almost done. The code is written just having some packaging issues. Will get it out by tomorrow at the latest.

  3. Steve Chapel

    I tried my Browser Mem Buster Test which simulates hours of browser usage. The regular Firefox 3 trunk build uses 122 MB after running the test and closing all but one tab. The special Firefox 3 beta 1 build uses 131 MB after exactly the same test. My opinion is that any perceived decrease in memory use is a placebo effect. I’ll post more results in this MozillaZine thread:

  4. Pete Kruckenberg

    @Jesse: Sorry, I don’t have a regular trunk 3.0b1 build to test with.

    I did try testing with 3.0a8, just a couple (10) pages quickly ran memory up to ~190MB and rising. Long-running Flash apps (Pandora, etc) seem to really eat up memory.

    This special build (again, I don’t have a regular 3.0b1 build) consistently keeps memory around 120-130MB with the same set of pages, even with Pandora running.

  5. Steve Chapel


    Could you list those pages that quickly ran through memory? If I can reproduce a problem, I’ll file a bug report. By Pandora, do you mean Pandora Radio? If so, I’m trying that now to see if I can reproduce a memory problem with the latest Firefox 3 nightly and Shockwave Flash 9.0 r47 on Windows XP.

  6. Steve Chapel

    After running Pandora Radio for over an hour (until it asked me to register) memory use hit a high of 118 MB. After closing all tabs but one open to the default home page, memory use is down to 50 MB. Long-running Flash apps don’t seem to be a problem for the regular Firefox 3 nightly builds, at least on Windows XP and with the latest Flash Player.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s