I thank you for your detailed questions and your enthusiasm to solve this hard but severe problem.
My request is not as specific as the new subject line suggests. I would say that as a worst case scenario, I am prepared to let the browser crash rather than having the browser crash my system. This is what effectively happens because that is happening if I am not spending an hour trying to figure out how to shut down applications one by one if there are still enough resources to let me do it. So crashing is still sub - standard compared with the Java applications I am referring to. I am using this scenario, the crash, just to explain how bad things really are. I am NOT requesting the crash behavior. In my subject line, I was requesting to "Fix Unbounded Resource Use". I do not appreciate being mocked here with a new subject line that I did not create.
1.: I am not familiar with the dependencies e.g. wrt 7. I would be counter-productive if I was specifying a component that would mainly be expensive to measure (responsible for a performance hit when being measured) while at the same time being of no great benefit.
2.: In this report, I am actually referring to memory consumption shown in Windows Task Manager against a single FireFox process. Sorry I failed to mention that. If additional processes each do not breach the same given limit, then that should be sufficient. I am against unbounded behavior only which is reckless. That is in line with many months of frequent memory issues, where an obvious memory leak was always limited to a single process where others were still running with moderate consumption somewhere at 500MB each. It is the situation where we have n times 500MB PLUS 4GB which is not acceptable.
3.: I don't know. I have some doubts about Task Manager showing graphics memory. I am concerned about memory leaks, and I have some doubts whether graphics memory is a candidate for what I am experiencing, and what others experience as well.
4.: Please refer to 3.
5.: I would refer to 3 if at all. I do not feel competent enough to answer this question.
6.: Probably not.
7.: From my perspective, practically speaking, I hope that question is a joke because you know if that was actually taking seconds, then why even discuss this. We don't need to explore the universe to diagnose the main culprit that causes this disaster, otherwise ... well I don't really want to go there.
I have reported multiple memory leaks, triggered by code hosted by multiple sites, and this did not go anywhere for more than a year. I hope that I am somehow making sense with my request in a way that you can facilitate a solution that solves the problem. As I wrote, I am aware already of two applications that communicate memory issues to the user, allowing for a graceful shutdown, and it does the trick. One of this is the NetBeans IDE, another one is the Thinkorswim trading platform. These are very big applications. A first step, addressing the biggest chunk of the well-known problems would be great.