Closed Bug 282600 Opened 20 years ago Closed 16 years ago

Large gif as a background image on the body causes performance issues

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: kevinar18, Unassigned)

References

()

Details

(Keywords: perf, regression)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050118 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050118 Firefox/1.0+

If you have the mentioned pcstats page open in another tabe, and you switch to
the tab, the browser locks up for several milliseconds.  Alternatively, if you
click on one of the poll options, the same thing happends each time you select
one of the radio options.

Reproducible: Always




Probably need to take some time to testcase this later on, but just getting the
report out of the way for now....
I found the cause to be the background image on the page.  It seems that using a
gif as a background image on the body tag causes these performance issues.


Additional notes:
The page does not only affect the browser, but other apps as well (such as
Windows Explorer).  For example, moving the Windows Explorer window over the top
of the web page causes a similar type of lag/hang.
Perhaps this a redraw issue in Firefox.

Detailed steps to reproduce:
1. Radio Button
Click on the radio button and as soon as you release the mouse, move the cursor.
 You will notice that the mouse lags for a few milliseconds.
2. Tab
Open a second tab and go to it.  Now click on the pcstats tab to go back to it
and as soon as you release the mouse button, move the mouse.  You will notice
that the mouse lags for a few milliseconds.
3. Other apps
Open up another program and resize it so that it fills only part of the screen.
 Make sure that the pcstats page is in the background.  Attempt to move the
window of the other program.  The window will lag in movement.
Keywords: perf
Summary: pcstats webpage locks up Firefox for several milliseconds → Using a gif as a background image on the body causes performance issues.
Not present in Firefox 0.8
Keywords -> regression

BTW, could this be a re-emergence of Bug 31044 (scrolling is affected here as well)?

Also, here's the system specs:
OS: Windows XP Home
Processor: P4 Willamette 1.5Ghz
Video Card: Nvidia Vanta
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050217 Firefox/1.0+
Keywords: regression
Sounds like a dup of bug 224572 or bug 261835.
This seems very close to bug 261835, but with one problem.  The site causes the
same problems in Firefox 1.0+ as this bug.  Howevever, when reverting back to
Phoenix 0.1, something interesting occurs.  Bug 261835 still has some of the
bugs present in Phoenix, while this bug has none of the bugs present.

BTW, I can't reproduce the scrolling issue mentioned in Bug 90198 (which bug
224572 is a duplicate of).

Further testing shows that this is caused by large gif images (not necessarily
transparent though).  However, once again, I can't figure out why this bug is
not present on old builds, while parts of Bug 261835 are.

Either I'm just making a mistake somewhere or there is a subtle difference.
Summary: Using a gif as a background image on the body causes performance issues. → Large gif as a background image on the body causes performance issues
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
WFM 

Kevin, markushuebner, does it work for you?

http://www.pcstats.com/articleview.cfm?articleID=1727
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060508 Minefield/3.0a1
3.2Ghz 

FWIW, testcase in Bug 261835 is no good
Assignee: bross2 → nobody
Status: ASSIGNED → NEW
Similar report in Bug 361754
Is this still happening?

Otherwise it should be closed.
Probably a DUPLICATE of Bug 361754. Can anyone confirm?
Mh, no sorry, it's too old. I think it's simple a WORKSFORME now.
closing WFM based on comment 6.  Can't get to URL anymore to confirm.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.