Open Bug 935330 Opened 11 years ago Updated 2 years ago

profiling eideticker cold startup says 4% of the time is spent reflowing the hidden window

Categories

(Core :: Layout, defect, P3)

ARM
Android
defect

Tracking

()

People

(Reporter: froydnj, Unassigned)

References

Details

(Keywords: perf)

Why is reflowing the hidden window taking so long?  I thought there was no content there...
I've got a patch in bug 926922 that can show the first action that trigger a layout/style flush that could help in finding whats triggered the reflow. Although in this case the question is probably how to avoid doing any processing for it at all.
Keywords: perf
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.