Comment Re:Memory Leaks Solved? (Score 1) 152
Not in the slightest. The blame is given to the application that is consuming the memory. That would be the browser in this case or the application running on an OS in your second example.
This bug has manifested itself in both Windows and OS X, in my case. (And the code base is shared mostly for both so that rules out it being an OS problem.
To answer your essential question--yes--without question an application should be written to be bulletproof. There should be no use case possible that causes your application to eat up unlimited memory. That is a defect, pure and simple.
I defy you to make your argument in any boardroom across the United States. I can see you making a presentation to a board of executives, explaining how your application did this or that horrid thing because--it was the web page's fault. Do you know what they call engineers who make that argument? Unemployed.
As you can see from the bug report that I personally participated in creating, including providing before and after memory dumps, it's clear I am invested in getting this Firefox memory leak fixed. It is plaguing users across the globe. Read the complaints on Mozilla's forum.
As for your comment that I'm making a mountain out of a mole hill--Firefox has been documented to consume 3GB of RAM in about 10 minutes. Other users who had left it open and idle over night have seen the same result.
Finally, I am expressing my point of view forcefully because you are trying to poo-poo my concern. This is a serious show-stopping defect in the application Firefox and it needs to get fixed unless Firefox wants to die a slow painful death.
This bug has manifested itself in both Windows and OS X, in my case. (And the code base is shared mostly for both so that rules out it being an OS problem.
To answer your essential question--yes--without question an application should be written to be bulletproof. There should be no use case possible that causes your application to eat up unlimited memory. That is a defect, pure and simple.
I defy you to make your argument in any boardroom across the United States. I can see you making a presentation to a board of executives, explaining how your application did this or that horrid thing because--it was the web page's fault. Do you know what they call engineers who make that argument? Unemployed.
As you can see from the bug report that I personally participated in creating, including providing before and after memory dumps, it's clear I am invested in getting this Firefox memory leak fixed. It is plaguing users across the globe. Read the complaints on Mozilla's forum.
As for your comment that I'm making a mountain out of a mole hill--Firefox has been documented to consume 3GB of RAM in about 10 minutes. Other users who had left it open and idle over night have seen the same result.
Finally, I am expressing my point of view forcefully because you are trying to poo-poo my concern. This is a serious show-stopping defect in the application Firefox and it needs to get fixed unless Firefox wants to die a slow painful death.