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.
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
Go to the Opera (Score:1)
Voted for it... (Score:1)
What bug? (Score:2)
How can you expect people to fix bugs this way.
Re:What bug? (Score:2)
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