Closed Bug 610443 Opened 14 years ago Closed 12 years ago

surfing on facebook slows down the more you get more news / scroll down

Categories

(Firefox :: General, defect)

3.6 Branch
x86_64
Windows 7
defect
Not set
major

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: ved61, Unassigned)

References

()

Details

(Keywords: perf)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12 GTB7.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12 GTB7.1

As you know there is an option in facebook to load more of news feeds the more you scroll down by clicking the link "Older posts" on the left side of the end of the news feeds page.
The more I scroll down (get older posts) the more firefox slows down. The text boxes of the "share boxes" - which are popping out by clicking the link "share" on the right bottom side of each post - are getting so slow that I can wait almost 30seconds after I finish writing a sentence to see the sentence in the textbox. Also the reactions and scrolling of ffirefox are getting slower.

Reproducible: Always

Steps to Reproduce:
1.Login to facebook and open news feed page
2.Get older posts (after 5 times the lag occurs but after 7 times it's extremely lagging)
Actual Results:  
Firefox slows down and lacks on reaction speed.

Expected Results:  
Should behave normally? As fast as ever..

I use the personas "Dark Fox", which you can see here: http://www.getpersonas.com/de/persona/5918
My computer has an intel Core i5 with 4 GB RAM and 500GB hdd space.. am using geforce gt240 (512mb).. no overtacting.. everythings fine.. original licensed windows 7 professional 64bit..
Can confirm this on Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 as well.
Version: unspecified → 3.6 Branch
ved61, db, do  you still see this when using version 6 or 7?
Keywords: perf
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.