Slashdot Mirror

← Back to Stories (view on slashdot.org)

Gran Paradiso Alpha 3

Posted by kdawson on from the car-insurance-not-included dept.

kbrosnan writes "Gran Paradiso Alpha 3 is a release of the Gecko rendering engine for testing purposes only. Here are the release notes. While this release uses the interface of Firefox, no significant interface changes have been made. These alpha releases focus on making improvements to the core elements: graphics, JavaScript, page rendering, etc."

8 of 187 comments (clear)

  1. Re:So.. by Jeffrey+Baker · · Score: 3, Insightful

    If they "fixed" this "leak", the other bunch of fucknozzles would come back asking "Why are back and forward so slow?!??". I think for the time being you people are slightly less annoying, so the "leak" stays.

  2. Re:Changes. by gerrysteele · · Score: 3, Insightful
    Perhaps someday soon they might invent some innovative technology to update you of these events.

    I would call it "The Status Bar".

  3. Re:Release notes and comments by CRCulver · · Score: 2, Insightful

    This is the common usage pattern. Uptime on desktop or notebook computers is generally low, and so Joe Average is not too likely to keep Firefox open for days or weeks and notice problematic memory usage. However, Joe Average would certainly notice sluggishness in the workings of the Back button.

  4. Re:So.. by Seumas · · Score: 1, Insightful

    A browser consuming hundreds of megs of ram is hardly a reasonable trade-off for a slightly faster back button that people rarely use to begin with.

  5. Even Mozilla guys ignore non-x86 Linux by cyba · · Score: 3, Insightful

    There's only single "Linux" download link that refers to Linux/x86 binary. If leading Free Software project doesn't treat non-x86 platforms seriously, how can we expect something different from e.g. hardware manufacturers?

  6. Re:Bug! by Nasarius · · Score: 2, Insightful

    So file it if it's not there already. That's what the alpha is for.

    --
    LOAD "SIG",8,1
  7. Re:Release notes and comments by LoveMe2Times · · Score: 1, Insightful

    Open a bunch of tabs that use plugins. I haven't pinned it down exactly, but one time a couple weeks ago I had Firefox using 1.5 GB of RAM. Yes. GIGABYTES. I was stunned, frankly. I had a dozen tabs open, tops. I was surfing Adobe's website, Verisign's website, googled a few things, so there were a couple of Flash movies playing and a PDF loaded. One and a half freakin gigabytes. The amount of swapping caused by this resulted in much anomalous behavior, and I was forced to use task manager to terminate the process. On another computer, Seamonkey regularly uses 500+ MB, but that's in large part due to the fact that I use the mail component. It is still quite ridiculous.

    As of right now, my firefox has 5 tabs open and is using about 73 MB. More revealingly, when I close 4 of them, leaving just this comment page, I'm still using 68 MB! My ./ tab does have a chunk of history, but I'm quite certain that 60 or more of those 68 MB have just been leaked away. And I only opened this firefox this afternoon. It hasn't been running for very long. For what it's worth, this is 1.5.0.10. The 1.5 GB problem was on 2.whatever-the-latest-is.

  8. Re:So.. by Man+of+E · · Score: 2, Insightful

    Other browsers have shown (Opera, Safari) that it's possible to have speedy back and forward buttons without taking up a gig of memory. You can claim that the Firefox back-forward code is so poorly written that it would have to be redone from the ground up, and that the developers consider a new spellchecker to be higher-priority than a time-consuming rewrite of this memory-hogging component. But please don't pretend that this is an intrinsic trade-off in browser design.

    --
    Ceci n'est pas une sig