Username or EmailPassword
I'm using the new 1.5 Beta, and after I open and download a couple score large images, my Windows XP system becomes seriously sluggish, until finally Windows says the virtual memory limit is too low. I have to at least close and reopen Firefox, or even reboot, to recover the system
Firefox needs to fix this problem. I was told most of the leaks would be fixed by 1.5, but that doesn't appear to be the case. The problem is less severe than it was in the earlier versions, but it has not been resolved by any means.
C'mon, guys! How long have memory leaks been known? Why are people still coding them? Start paying attention to code quality before features or OSS will start looking and acting like Microsoft products! Bloat, instability and insecurity will follow!
C'mon, guys! How long have memory leaks been known? Why are people still coding them?
That's like saying "How long have car crashes been known? Why are people still having them?"
When working on a project that requires a large team, no matter how hard you try, there will be occasions where a person doesn't realize the implications of what they're doing on what other people are doing. You can't avoid problems, you can only try to minimize how often they happen.
I would agree when it comes to bugs, but NOT any sort of memory leak. Memory leaks are usually pretty easy to detect, trace and track down, by using third party tools. Bugs are things that can't be tested against sometimes. Memory leaks can be. There is no excuse.
Though there could be a leak (see my other comment, which I'll write in a minute), it CANNOT be the issue Federico is dealing with, as Windows XP do NOT have an X server .