Digg.com "digg this" script causes momentary large memory spikes (50+ MB) when called many times in a web page

RESOLVED INCOMPLETE

Status

()

Firefox
General
RESOLVED INCOMPLETE
10 years ago
9 years ago

People

(Reporter: Raif Atef Wasef, Unassigned)

Tracking

({footprint, perf, regression})

Trunk
x86
Windows XP
footprint, perf, regression
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008050206 Minefield/3.0pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008050206 Minefield/3.0pre

There's a strange issue in this site: http://isohunt.com/, while it is loading (look at the task manager, Firefox.exe mem usage suddenly jumps by 40-50 MB to over 140 MB and then suddenly drops back to normal, this mem spike causes a big swap impact (on my 256 MB RAM laptop). This is more apparent with a slower internet connection.

The problem seems to happen due to the Digg This button scripts: http://digg.com/tools/diggthis.js
which is repeatedly called by script tags in the body of the page many times.

Problem happens in safe mode as well. And with a fresh new profile. IE7 does not have this issue (but is spikes the CPU for a while). Firefox 2 works correctly as well. 

If I Adblock that script, (diggthis.js), the problem mostly goes away.

Reproducible: Always

Steps to Reproduce:
1. Start Minefield on a fresh profile or in safe mode.
2. Open Task manager and look at the "firefox.exe" memory usage and VM size.
3. Go to http://isohunt.com/ on a slow internet connection and watch task manager.
Actual Results:  
When the status bar says "Read digg.com ..." Firefox memory usage increases by 50-60 MB for some seconds and then drops back to normal.

Expected Results:  
There is nothing on that page that would warrant this huge memory allocation, it should not behave like this.
(Reporter)

Updated

10 years ago
Keywords: perf, regression
Version: unspecified → Trunk
(Reporter)

Comment 1

10 years ago
I tried to find a regression range and went as far back as firefox 3 beta 2 and it was still there although manifesting to a lesser degree (lower spike amount).

Updated

10 years ago
Duplicate of this bug: 432103

Comment 3

10 years ago
See bug 427396 for an extreme example.
Blocks: 427396
Keywords: footprint

Comment 4

10 years ago
Not to state the obvious, but this script is everywhere.  This bug should probably also have the top100 and top500 keywords added.  (for digg.com and isohunt.com, respectively)

I don't get enough of a hit from this to ask for blocking of RC1, but I'd guess this is probably a good candidate for a blocker of the final release.

Comment 5

9 years ago
don't see this with Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3pre) Gecko/20081222 Shiretoko/3.1b3pre
(Reporter)

Comment 6

9 years ago
I can no longer see this happening at the original URL although viewing the source of the page shows that the diggthis.js script is no longer present. So I can't really say that this bug is gone.

I tried the page with latest trunk and with both jits enabled:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20081227 Minefield/3.2a1pre

Comment 7

9 years ago
incomplete without testcase
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.