Closed Bug 1463 Opened 26 years ago Closed 26 years ago

ss: XPViewer sucks resources resizing/maximizing on win95

Categories

(Core :: Layout, defect, P1)

x86
Windows 95
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: paulmac, Assigned: law)

References

Details

Resources go to 0% after resizing the default home page a couple times. Verified on two win95 machines (with lots of RAM). After closing xpviewer, resources return to normal. 11/19 build.
Summary: XPViewer sucks resources resizing/maximizing on win95 → ss: XPViewer sucks resources resizing/maximizing on win95
Setting to stopship since it makes xpviewer virtually unusable on win95
Status: NEW → ASSIGNED
We've plugged a couple of leaks and things are looking better. Still a ways to go, however.
*** Bug 1452 has been marked as a duplicate of this bug. ***
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Checked it out and we're looking much better. No observable resource leaks on Windows98.
Per bug mtg today, law belives this is fixed. But he will check out first before moving to Resolved/Fixed for QA to Verify.
Status: RESOLVED → VERIFIED
It is much better now, though there are still small leaks. However, I can get through the top 25 sites without running out of resources (barely) on my wimpy 48 Mb machine, so it's no longer a showstopper. Will mark this bug verified and open another one for the slow leaks.
the remaining leaks have been tracked down by rick potts and appear to be the result of form element controls having too many references to other objects.
One note: I suspect the small leaks that still exist would be due to leaks in the page rendering (rather than the chrome, as was the case previously). A good test of that theory is to see if the plain viewer demonstrates the same leaks.
we already did that today, and the only leaks that still appear happen when you go to pages with form elements. i believe rick found the extra addref().
*** Bug 1238 has been marked as a duplicate of this bug. ***
Inserting Milestone info.
You need to log in before you can comment on or make changes to this bug.