Closed Bug 70290 Opened 24 years ago Closed 24 years ago

90% of time spent activating mail window is in ReResolveStyleContext

Categories

(Core :: CSS Parsing and Computation, defect)

Product:
Core
Component:
CSS Parsing and Computation
Platform:
PowerPC
Mac System 9.x
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
VERIFIED WONTFIX

People

(Reporter: mikepinkerton, Assigned: attinasi)

References

Details

(Keywords: perf)

when profile the 'activate' phase of bringing a mail window to the fg, 90% of the time is spent in ReResolveStyleContext, probably because of use of :focus. Note that this is easily twice the time spent than a similar profile of bringing a navigator window to the fg. It is very noticeable, even in optimized builds on my fast mac.
Blocks: 48274
Probably a lot of attribute tweaking happening as a result of command updating here too.
Are you speaking about the mail 3-pane window?
yes, the 3-pane mail window
I can profile this, but if there is a lot of style resolution going on the most likely reason is that there are evil style rules (like *:active) or lots resolution getting triggered due to attribute or content changes. Please indicate what stylesheets apply here so I can look at the rules in addition to the profiling. Is this only on the Mac? If so, some profile data would be nice too since I cannot currently profile on the Mac. Also, what is the 'bug' here? How much time is reasonable for resolving style? Thanks.
Still looking for some information here... see my prior comment please.
Outliner will make this bug obsolete. IMO this bug should just be closed as WONTFIX, since the new tree widget solves this problem and will be landing during the 0.8.1 freeze.
I can buy that - Thanks David! Marking WONTFIX since David's new outliner will make this obsolete. If the reporter or anybody else disagrees with the resolution, please reopen and provide mo' data.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
The old tree widget has some skanky :focus rules that probably caused the performance hit.
you're _sure_ about that? totally _sure_?
v
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.