Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

yudel (1014)

yudel
  (email not shown publicly)
http://www.shmoozenet.com/yudel

Journal of yudel (1014)

Monday December 26, 2005
10:16 AM

firefox sucks

[ #28130 ]
Take a look at https://bugzilla.mozilla.org/show_bug.cgi?id=213534 This is a two-year-old bug, where closing a tab doesn't release memory.

Firefox doesn't really suck, but this bug does, and I'm getting desperate enough to use any forum I can to spread the word about it.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Vote registered as ordered sir!
  • I looked at that page, I all I can see is some handwaving. In other words: it's not even proven that this is a (simply reproducable) bug. Yes, the memory usage as demonstrated is excessive, but is there a memory leak? I don't know.

    How can you expect people to fix bugs this way.
    • That's the problem; I'm a user, here, not a developer.

      Whether it's technically a memory leak that closing a tab doesn't release memory doesn't change the fact that it's a problematic situation.

      Obviously, the best way for me to get the bug fixed would be to figure out who actually owns the relevant piece of code... which is more hackery than I would prefer to do. It is, certainly, a possibility down the road, particularly if I fail in my cheap, thuggish campaign to bring the bug to the attention of the power