Linked by Thom Holwerda on Fri 8th Sep 2006 20:54 UTC
Permalink for comment 160682
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
Linked by Thom Holwerda on 05/15/13 23:03 UTC
More News »
Sponsored Links



Member since:
2005-07-06
Problems that can readily be found can readily be fixed.
Hahaha. So that's why it took so long for Mozilla to even admit there is a memory leak let alone fix it? Stop living in the dream world. Go to bugzilla. Some bugs are 3+ years old, but only because the developers for some reason or another, don't want to fix them, they're not bugs.