Quote:
|
I'm hoping that they get it fixed before 5.5 final (preferably for the next beta would be nice!) as this issue has been really annoying to me ever since the first sneakypeek.
|
Honestly, I'm not holding my breath. Every browser I've ever used has suffered from serious memory leaks and concomitant eventual slowdowns. OG identified a major bug related to JS, but it's just one bug on top of what I'm guessing are many, many more. Barring radical changes in development techniques and tools, priorities, the OS, or some combination of these, I don't expect this problem to go away.
That said, there is hope. A while back, the Safari team went on a crusade against memory leaks. They were actively soliciting feedback in this area, and they crushed literally thousands of memory-related bugs. That's wonderful, but I doubt they can keep it up in the face of other issues that are more visible to the average user, plus the demands of adding new features.