184263 - Meta Refresh Occurs at 1/100 of the specified Interval

Status: RESOLVED WORKSFORME

(Core :: DOM: Navigation, defect)

Description

[Thomas E. Link]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130

The meta refresh specified at http://www.wral.com/?cpt=express is 
<meta http-equiv="Refresh" content="1200">
But on one machine - Windows 2000 with SP3 and all current hotfixes this page
refreshes every 20-30 seconds. It appears that there is something wrong in the
timer function that is connected just with this one machine, because other
things seem to also fail. 

For example, at www.gmcard.com, if you login and then attempt any transactions,
the site informs me that the login has expired and I need to login again. There
they have <meta http-equiv='refresh' content='900; url=CustomerCare?cmd_LogOff=' />

I have observed this ONLY ON THIS ONE MACHINE, but with every recent version of
Mozilla  that I have tried.

I have completely deleted Mozilla and reinstalled. I have removed all plugins. I
have deleted all profiles. None of the above has had any affect on the problem.

I have identical installs of Mozilla on other machines and I have never observed
anything like this.

I have reviewed the bug (170021) about meta refresh occuring continuously but
this is not the case. There is a distinct delay between the refreshes, and there
is nothing coded incorrectly in the meta tag (that I can identify).

Reproducible: Always

Steps to Reproduce:
1.Connect to websites listed.



Actual Results:  
Refresh occurs very quickly. Estimated to be about 1/100 of the specified
interval. The site listed has 20 minutes specified (1200 seconds) and instead
the refresh occurs every 12 seconds (estimated).

Expected Results:  
Refresh in 20 minutes.

Comment 1

[R.K.Aa.]

What kind of bandwidth do you have there? (The pause inbetween refreshes may not
be visible on a slow connection)

Comment 2

[Thomas E. Link]

Cable Modem. The page loads in a second or so.

The 20 minute meta refresh time is turned into 12 seconds.

Comment 3

[Christian :Biesinger (don't email me, ping me on IRC)]

related: bug 187512

Comment 4

[Thomas E. Link]

I see with the "related" bug that I am not the only one with this problem. There
are other symptoms, such as erratic cursor blinking, and pages expiring. When I
log into www.gmcard.com, I have about 3 seconds before my login on that site
expires. At https://airmail.trondent.com/default.asp I have a similar 3 seconds
before my login on that site expires.

I have tried to investigate in the source code how the "sleep" is processed and
it looks like the "snooze()" function is called. But I can't locate this
anywhere. Can you tell me where I might find this?

The machine with a problem is running Win2K at the latest service level, with
LOTS of software installed on it. No other machine I have (I have 5 others on
various platforms) shows this problem.

Tom Link

Comment 5

[Thomas E. Link]

One more additional symptom. On the http://www.palmsource.com/ page is a news
field (near the bottom) which is an image that is changed via javascript. The
script has a delay time of 2500ms. On this machine with this problem, the image
is changed so rapidly that it cannot be read (perhaps 100 times per second).

I should mention also that the problem persists in the 1.3beta.

Tom Link

Comment 6

[Jon Henry]

Thomas: Are you sure that this is a problem with Mozilla and not something going
screwy with that specific computer? Do the various sites mentioned here work
properly in Internet Explorer (as well as a recent Mozilla build), for example?
It's quite possible it's a bug in Mozilla, but we should first rule out other
factors, like the system timer somehow running too fast. Thanks for any new
information.

Comment 7

[Thomas E. Link]

It absolutely must be a system-specific problem, but what? This has persisted
across multiple Mozilla versions. Netscape 4.7 and IE 6 work fine on the same
machine. No other applications display anything like this.

Does Mozilla reach into some Microsquish DLL to run a timing loop? If so, I can
look at the version. I have completely removed Mozilla several times and this
problem has always been there. I am currently using 1.4.

The machine is a 450mhz IBM with 256meg and AMD processor running with Windoze
2000 with ALL MS fixes.

Comment 8

[Asa Dotzler [:asa]]

->Docshell

Comment 9

[Robert Mohr]

*** Bug 224899 has been marked as a duplicate of this bug. ***

Comment 10

[Dory]

I have noticed this bug on this site:  http://heraldsun.news.com.au/

The site refreshes every few seconds.  
My system is Windows 2000 SP4 with all hotfixes.

The affected system is an AMD K6III 400 running on a Gigabyte MB.
There is not much software on this machine:  Norton Antivirus, Agnitum Outpost
firewall, Office 2000.  I recently installed Win2000 onto an empty hard drive.

I have reproduced this bug on Mozilla 1.4, 1.5, and 1.6a, as well as Phoenix 0.7

I can successfully view this page on IE 6.0 SP1.

Comment 11

[Asa Dotzler [:asa]]

*** Bug 187512 has been marked as a duplicate of this bug. ***

Comment 12

[Yuan Qi]

*** Bug 280147 has been marked as a duplicate of this bug. ***

Comment 13

[Yuan Qi]

Confirmed for the Herald Sun page.

I also notice problems with http://www.wired.com as well as http://mail.yahoo.com

It seems most of the constant refresh bugs are actually dupes of this bug.

This is likely to be a win2k (and perhaps winxp) specific bug, as I didn't
notice problems with the above pages on win9x.

Comment 14

[Yuan Qi]

This is a highly annoying bug for those who are affected.

This bug might only affect those with AMD K6 CPUs (My computer's CPU is AMD K6II
500) running win2k

Comment 15

[u88484]

Status=>New based on dupes and the comments here

Comment 16

[Yuan Qi]

Maybe this bug should be assigned to someone else.

It's almost been three years since this bug was first reported and the assignee 
hasn't made a comment yet about the cause of this bug or even how to narrow it 
down.

Also, many people have reported timing bugs on AMD K6 machines running Win2k. 
Maybe these bugs should be merged together.

Comment 17

[timeless]

[e-mail]: sure, gladly, whenever you want to take a
bug, just speak up. don't hessitate to volunteer. if you need help getting
started, #developers will gladly help

Comment 18

[Thomas E. Link]

The hardware that showed this bug is no longer in service.