User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; zh-CN; rv:220.127.116.11) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:18.104.22.168) Gecko/20090921 Moblin/3.5.2-4.1.moblin2 Shiretoko/3.5.2 visit www.nytimes.com via proxy, after the website is fully loaded(the button in location bar changed to "refresh"),press refresh button to refresh the website and scroll up/down for a few seconds, then the scrolling wil be locked up. Reproducible: Sometimes Steps to Reproduce: 1.setup proxy then open www.nytimes.com 2.wait 20 seconds after the website is fully loaded 3.Press refresh button to refresh the website 4.scroll up/down for a few seconds, try to click something 5.It can't respond user input and the scrolling will be locked up for some time 6.Need to wait about 3 minutes then the scrolling will be unlocked 7.I found this site works fine if not using proxy Actual Results: it can't respond user input and the scrolling will be locked up for some time Expected Results: The scrolling should not be locked up and it should reponse to user input.
Which proxy server software ?
(In reply to comment #1) > Which proxy server software ? Squid
Squid should not cause any issues. Can you please try the Firefox safemode to be sure that this isn't caused by an extension ? http://support.mozilla.com/en-US/kb/Safe%20Mode I have no proxy here to test it myself...
Component: General → Networking
Product: Firefox → Core
QA Contact: general → networking
Version: 3.5 Branch → 1.9.1 Branch
I have tried the firefox safemode and repeated the steps today. But the result is same. It can't respond user input and the scrolling will be locked up for about 2-3 minutes. Then the page will be back from freeze mode and response to the input , the scrolling will also be unlocked.
Is this still a problem ?
I going to mark this incomplete - the test wfm and it lacks further input from original reporter. it could also be a dup of sorts of 648603 where some ad servers nyt uses were hanging and monopolizing the small proxy connection pool.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.