Bugzilla

(In reply to Bodea Daniel [:danibodea] from comment #79)
> I do not know how to confirm these results. How exactly do you verify them?

You can compare results before and after long session browsing in Task Manager and seeing how much % of memory Mozilla Firefox is using. Substitute for this could be external software named Process Explorer. Showing and saving memory reports in about:memory for Mozilla Firefox developers is next step.


> Furthermore, this bug appears to have a regression range provided already. The "regressionwindow-wanted" tag should be removed. Is the regression range provided incorrect?

(In reply to Bodea Daniel [:danibodea] from comment #79)
> I do not know how to confirm these results. How exactly do you verify them?

You can compare results before and after long session browsing in Task Manager and see how many % of memory Mozilla Firefox is using. Substitute for this could be using external software named Process Explorer. Showing and saving memory reports in about:memory for Mozilla Firefox developers for deep analyzing is next step.

(In reply to Bodea Daniel [:danibodea] from comment #79)
> Furthermore, this bug appears to have a regression range provided already. The "regressionwindow-wanted" tag should be removed. Is the regression range provided incorrect?

Yes, regression range is provided, but it's kinda vast and broad. It's still not known which patch from which bug caused this bug from that regression range. That's why "regressionwindow-wanted" tag isn't removed.