Closed Bug 299569 Opened 19 years ago Closed 17 years ago

Performing any action on Bungie.net causes Camino to hang for 20-30 seconds

Categories

(Camino Graveyard :: General, defect)

Product:
Camino Graveyard
Component:
General
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: olly, Unassigned)

References

(
URL
)

Details

(Keywords: perf) 

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050531 Camino/0.9+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050531 Camino/0.9+

When visiting Bungie.net or any pages on that site the page loads correctly but
any action (scrolling the page, clicking a link, etc) will make Camino
"beachball" for around 30 seconds. This will also happen if you open a
Bungie.net page in a background tab and attempt to click it, and then again if
you try to scroll when the tab opens.

Reproducible: Always

Steps to Reproduce:
1. Visit http://www.bungie.net and wait for page to load.
2. Attempt to scroll the page or click a link (this should cause the first hang).
3. Middle-click a link to open it in a new tab.
4. Attempt to change to the new tab (this should cause another hang).
Actual Results:  
Two hangs in the noted places, and a third when closing the new tab to return to
the first.

Expected Results:  
Pages should be changed and scrolled without the software hanging.
My guess is our awful redraw performance in some situations + the many position:
fixed; and animated elements on the page.
URL: http://www.bungie.net → http://www.bungie.net/
I only get a beachball for a few seconds, probably due to a nice userContent.css.  

Wevah: should this be duped to the animated elements bug or is it different
enough to be confirmed on its own?
It's very possibly a dupe. If so, this is definitely a good example as an
extreme case.

I guess I'll just have to check things with QuartzDebug a little and remove some
elements one-by-one to see for sure, though.
Yet another example of our redraw mess. On my dual G5 this page used 100% of my
cpu's when I scrolled. WE SUCK

*** This bug has been marked as a duplicate of 280982 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
I'm unduping this one, too.  It's manifestly *not* bug 280982 comment 0, but
that's all I can say; someone who understands Shark and who can take apart pages
should have a look.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Smokey don't worry this really is that rectangle redraw ug, investigation with
Quartz Debug showed we are doing a lot of repaint stuff. Another part of the
slowdodn on this webpage is the fact that they use some div's that are overlain
and gecko just isn't really fast at rendering that.
Some quick profiling shows that image tiling is a large part of the slowdown.
The 1600x4 background image may contribute (bug 295737).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: perf
This is better after all the recent perf fixes, but I still beachball some, like
when loading one of the "full story" pages (1.33 GHz G4).
(In reply to comment #7)
> Some quick profiling shows that image tiling is a large part of the slowdown.
> The 1600x4 background image may contribute (bug 295737).

I'll have a look at this with the tiling build in bug 295737, too, when I get a
chance to grab it.
Depends on: 295737
I don't notice any improvement with the tiling build over what I noted in
comment 8, unfortunately.  I still beachball trying to scroll one of the "full
stories" linked from the main bungie.net page.
Assignee: pinkerton → sfraser_bugs
The perf issues on bungie.net seems to be caused by a lot of drawing, especially
when scrolling, because the page has a large number of fixed position elements.
Many of these have background-image CSS so we do some image tiling for them.
Theare are also animated gifs.

It's probably worse in Camino because we're still being bitten by bug 166932 on
this page.
*** Bug 327410 has been marked as a duplicate of this bug. ***
Things seem reasonable in a trunk build; it's not exactly snappy, but no worse than other browsers. Is anyone still seeing beachballing with trunk builds?
Assignee: sfraser_bugs → nobody
QA Contact: general
Sounds like not, so closing. If anyone sees this in trunk, feel free to re-open.
Status: NEW → RESOLVED
Closed: 19 years ago → 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.