Closed
Bug 70139
Opened 25 years ago
Closed 23 years ago
Every window filled with broken window image after a long usage.
Categories
(Core :: XUL, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
Future
People
(Reporter: tarahim, Assigned: dcone)
Details
Attachments
(1 file)
|
66.10 KB,
image/jpeg
|
Details |
2001022304 trunk for MacOS.
It started in this or around 0221 build.
After a long surfing with a lot of open windows, a window fails to load an image
within a page (JS coded?) and then, the background of the window leaks to the
entire window and every window is filled with the image of this window content.
It is a little bit like bug 55622 and bug 55982.
| Reporter | ||
Comment 1•25 years ago
|
||
pinkerton, who should own this?
Assignee: asa → trudelle
Severity: critical → major
Component: Browser-General → XP Toolkit/Widgets
QA Contact: doronr → jrgm
Updated•25 years ago
|
Assignee: trudelle → sfraser
Comment 3•25 years ago
|
||
hrm, sfraser is the de-facto owner of this kind of stuff in general, pushing to
him for better triage.
Comment 4•25 years ago
|
||
How did you determine that memory had run out? Was the heap full? Or was there no
temp mem left?
| Reporter | ||
Comment 5•25 years ago
|
||
True, I did not really check the memory amount. I usually see that the memory
usage for both finder(system) and Mozilla go up and then weird things start to
happen.
Removing reference to the memory from Summary.
I will check it when it happens again. So far, I have experienced this only
twice in the same build. BTW, the bug is not corrected by closing the windows.
Relaunching is necessary.
Summary: Every window filled with broken window image after memory runs out. → Every window filled with broken window image after a long usage.
| Reporter | ||
Comment 6•25 years ago
|
||
Indeed, the memory did not run out before this bug hit for the third time.
Mozilla crashed after I took a screen shot, probably during check mail. Memory
was a plenty as recorded by Macsbug:
System heap high free space + TempMem low free space = #49105632 (#46M)
| Reporter | ||
Comment 7•25 years ago
|
||
Yet of course it is probable that the memory space was fragmented and free
memory for Mozilla ran out in the above example. I had various apps. launched
and used during the time.
| Reporter | ||
Comment 8•25 years ago
|
||
This one really looks similar to bug 55622 and bug 55982.
Once you close all the windows and open a new one, the new window is still the
same garbage. At this point, the bar in showing the memory usage in "About this
Computer" window is filled to the right edge.
Then you reduce the window size and then the window returns to normal.
Then the memory usage indicator also shows some unused space in "About this
Computer" window.
| Reporter | ||
Comment 10•25 years ago
|
||
Yup. It has just happened in 2001032418 build.
Comment 12•24 years ago
|
||
This sounds like double-buffering gets whacked to me. -> dcone.
Assignee: sfraser → dcone
Comment 14•24 years ago
|
||
This bug report is from Feb 25, so, no, this is not fallout from the new imglib
Updated•24 years ago
|
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Updated•24 years ago
|
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Updated•24 years ago
|
Target Milestone: mozilla0.9.3 → mozilla0.9.4
| Assignee | ||
Updated•24 years ago
|
Target Milestone: mozilla0.9.4 → mozilla0.9.5
Comment 16•24 years ago
|
||
0.9.5 is out the door. bumping TM up by one.
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Updated•24 years ago
|
Target Milestone: mozilla0.9.6 → mozilla0.9.8
| Assignee | ||
Updated•24 years ago
|
Target Milestone: mozilla0.9.8 → mozilla0.9.9
Updated•24 years ago
|
Target Milestone: mozilla0.9.9 → Future
| Reporter | ||
Comment 17•23 years ago
|
||
Have not seen this for a while.
I guess I can mark this WFM.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•