Slashdot Mirror

← Back to Domains

Domain: pavlov.net

Stories and comments across the archive that link to pavlov.net.

Comments · 55

  1. Re:File bug reports rather than whine on Slashdot by ozmanjusri · · Score: 3, Informative · on Google's Shadow Over Firefox
    Second, there is no sign of any "memory gobbling bug" that I can see

    There is, sort of.

    Stuart Parmenter has found memory fragmentation happening which makes it look like FF is consuming lots of RAM.

    Basically, because FF loads many components, including Javascript, strings, sqlite, CSS parsing, HTML parsing, etc, the RAM between each used block may be unavailable as contiguous memory even if FF isn't using it. The problem is showing up mainly on Windows because the 2.6 and above kernels have built-in RAM defragging, but it could catch a Linux user if an app requests more RAM before the kernel can make it available..

  2. Re:File bug reports rather than whine on Slashdot by bunratty · · Score: 1 · on Google's Shadow Over Firefox

    No, developers have not pretended that memory leaks aren't there. There are plenty that are easily reproducible, and about 100 memory leaks have been fixed in the past year. In fact, they can find so few leaks now that they've needed to look at other ways of reducing memory use. Please stop fabricating lies about memory problems in Firefox. If you want to point out a specific "memory gobbling" or CPU hogging bug, fine, let's have it so a bug report can be filed and the problem fixed.

  3. File bug reports rather than whine on Slashdot by bunratty · · Score: 5, Informative · on Google's Shadow Over Firefox

    The Firefox CPU hogging and memory gobbling bug would take some serious troubleshooting to find, and no one wants to do the work, apparently.

    First, the Firefox CPU bug you've been complaining about (Firefox consumers lots of CPU after the computer wakes up from standby or hibernate) was fixed in Firefox 2.0.0.8. If you're still having any problems with the latest release of Firefox, let developers know by filing a proper bug report, including steps to reproduce the problem.

    Second, there is no sign of any "memory gobbling bug" that I can see, just a few little leaks here and there and some memory fragmentation. If you're still having any problems with the latest release of Firefox, let developers know by filing a proper bug report, including steps to reproduce the problem.

  4. Re:Picture Quality by stu42j · · Score: 1 · on Book Excerpts: OOo Draw Documents with Imagination

    Do any browsers handle resizing more gracefully?

    Well, certainly not IE. I don't know about any others. Firefox is moving to Cairo for graphics rendering which will allow better image scaling, amoung other things.

    http://pavlov.net/blog/archives/2005/08/more_new_g raphi.html

  5. Re:Bye bye MNG. by pipacs · · Score: 1 · on Presenting APNG: Like MNG, Only Better
    I couldn't find any justification for this hack except that the Mozilla MNG decoder is too big - (they say 200 k+.

    How about streamlining the existing decoder instead, aiming for MNG-VLC only, a basic subset of MNG, already covered by the MNG standard, and not much different from what's proposed in APNG.

    Hacking around standards is so IE-ish...