Closed Bug 129806 Opened 22 years ago Closed 21 years ago

Chainging font size is very slow

Categories

(Core :: Layout, defect, P2)

defect

Tracking

()

RESOLVED DUPLICATE of bug 140391
Future

People

(Reporter: ezh, Assigned: attinasi)

References

()

Details

(Keywords: perf, testcase)

1. Load the page
2. Press CTRL-+ for changing font size.
3. It takes about 4-5 sec. on my Duron 950. 

Opera and ie are doing it much faster.

moz 2002030703
layout.
Assignee: asa → attinasi
Component: Browser-General → Layout
QA Contact: doronr → petersen
Keywords: perf
Changing QA contact
QA Contact: petersen → amar
Priority: -- → P2
Target Milestone: --- → Future
 Confirmed that it takes 10 sec on my machine with 600 MHz CPU and 126 mb ram.
 
Keywords: testcase
just hit this on my 1.5 GHz machine.  froze the app for about 10 seconds!

here's what I saw in the console, several times.

WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
WARNING: empty damage rect: update caller to avoid fcn call overhead, file c:/bu
ilds/buffy/mozilla/layout/html/base/src/nsFrame.cpp, line 2535
*** Forcing reframe! ***
*** Forcing reframe! ***
*** Forcing reframe! ***
*** Forcing reframe! ***
*** Forcing reframe! ***
*** Forcing reframe! ***
*** Forcing reframe! ***
*** Forcing reframe! ***
*** Forcing reframe! ***
*** Forcing reframe! ***
*** Forcing reframe! ***
*** Forcing reframe! ***

to be fair, I had mail open, and a browser window with about 6 tabs.

QA Contact: amar → petersen
more like 5 seconds, not 10.  but still long enough to notice.
The heart of it is that reflowing the whole page (and it's not a small page)
takes a while...  
OS: Windows 2000 → All
Hardware: PC → All
Whiteboard: DUPEME

*** This bug has been marked as a duplicate of 140391 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.