242823 - Page doesn't appear at once, takes very long to render

Status: RESOLVED FIXED

(Core :: Web Painting, defect)

Description

[Frank Wein [:mcsmurf]]

To reproduce do this:
1. Load http://bugzilla.mozilla.org/
2. Load http://bugzilla.mozilla.org/query.cgi
3. Go back
4. Go forward

Watch that page rendering takes very long, it seems to finished loading, but the
website itself will render about 1-2 seconds later. You can only see the caret
blinking while this 1-2 seconds. Now you can go back and forward again, probably
you will see the same again. At the 2nd time i went back&forward it seems a part
of the image at the top appeared first and then the rest. Happens with a current
cvs trunk build.

Comment 1

[Frank Wein [:mcsmurf]]

*** Bug 242822 has been marked as a duplicate of this bug. ***

Comment 2

[Frank Wein [:mcsmurf]]

This can be reproduced with many sites afais. Another example would be go to
heise.de, click link at the top "Telepolis", go back, go forward, rendering
happen only after 1-2 seconds.

Comment 3

[Charles Capps]

I also see this on Firefox 20040506 on Win2k.

Selecting text causes that area of the page to appear.  If the page is scrolled,
the newly scrolled area is properly rendered.

There does not appear to be any extra CPU use while the page is invisible.

Comment 4

[Frank Wein [:mcsmurf]]

Probably this regressedf in the last few days, i'll try to find out.

Comment 5

[Frank Wein [:mcsmurf]]

This seem to broke between 2004050509 and 2004050609. To reproduce it seems you
have to use tabbed browsing, so to reproduce the steps in Comment 0 you have to
open at least 2 tabs (the one tab can be empty, in the other you reproduce the
bug). Bonsai link for checkins
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=SeaMonkeyAll&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2004%2F05%2F05+08%3A30%3A00&maxdate=2004%2F05%2F06+09%3A00%3A00&cvsroot=%2Fcvsroot

Comment 6

[Robert O'Callahan (:roc) (email my personal email if necessary)]

if you move the window offscreen and then back onscreen, does it repaint
immediately?

Comment 7

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Also, if you have a debug build and know how to turn paint flashing on, try that
and tell me what the results are.

Comment 8

[Frank Wein [:mcsmurf]]

(In reply to comment #6)
> if you move the window offscreen and then back onscreen, does it repaint
> immediately?

If i reproduce the bug, move the window offscreen and onscreen, the part that
was offscreen, got rendered. Also i move the window offscreen, reproduce the bug
and move the window onscreen, the part that was offscreen got rendered.

Comment 9

[Frank Wein [:mcsmurf]]

(In reply to comment #7)
> Also, if you have a debug build and know how to turn paint flashing on, try that
> and tell me what the results are.

It flashs twice, first when going forward to the page (also there is only the
area instead of page, maybe some animated gifs (or flash animations, etc.)
appear in this white area when they'll move. And it flashes a second time when
the rest of the page is displayed.

Comment 10

[Frank Wein [:mcsmurf]]

btw: What i also have noticed (and i think this is related to this bug) is that
when i submit a bug report, then the "Changes submitted for bug xyz[...]"
appears not correctly. First only the buttom of the page appears (the bugzilla
toolbar with Actions and My Querys) and then after some seconds the table with
"Changes submitted for bug 242823
Email sent to: [...] "

Comment 11

[Ali Ebrahim]

I'm pretty sure I've seen this on my Linux GTK2+Xft builds too.

Comment 12

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Apparently some invalidates are being lost.

Comment 13

[Robert O'Callahan (:roc) (email my personal email if necessary)]

I'm not sure I can reproduce this.

Comment 14

[Jesse Ruderman]

roc backed out the change that caused this bug:
http://bugzilla.mozilla.org/show_bug.cgi?id=242856#c67

Comment 15

[Frank Wein [:mcsmurf]]

has been fixed, too