Closed Bug 113334 Opened 23 years ago Closed 17 years ago

Examine amount of painting during message display

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID
mozilla1.2alpha

People

(Reporter: mscott, Assigned: mscott)

References

Details

(Keywords: perf)

Attachments

(1 file)

Using a stand alone message window, I turned on paint dumping to see how many
paints we try to do when displaying a message. I used a stand alone message in
order to rule out any folder pane or outliner painting. 

Displaying our standard test message causes 7 paints to happen. I then tried to
figure out how many paints are going towards the XUL header overlay vs. the HTML
body. To do that, I removed the header overlay broadcasting so only the message
body was displayed. I still saw 7 paints. This means all of the painting is
being caused by loading the body into the iframe. 

I wonder if the format of the HTML we are giving the parser triggers excessive
painting or if 7 is a reasonable # of paints for my example document.
marking dependent on the mail perf bug. 
Blocks: 22960
Status: NEW → ASSIGNED
Keywords: nsbeta1, perf
Target Milestone: --- → mozilla0.9.7
QA Contact: esther → stephend
i'll keep looking at this in 098.
Target Milestone: mozilla0.9.7 → mozilla0.9.8
adding a plus in case you still think we need to look at this.
Keywords: nsbeta1nsbeta1+
moving to 1.2 since message display perf investigation will be put on hold for a
while.  You can move this back if you think this needs to be fixed.
Target Milestone: mozilla0.9.8 → mozilla1.2
Blocks: 122274
Keywords: nsbeta1+nsbeta1-
Product: Browser → Seamonkey
Scott thinks "too old to be relevant", so closing INVALID. Please reopen if you think otherwise.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: