179287 - IFRAME continues refreshing/reloading after page is no longer displayed

Status: RESOLVED DUPLICATE of bug 194994

(SeaMonkey :: General, defect)

Description

[Sean Harding]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2b) Gecko/20021105
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2b) Gecko/20021105

The page at
http://sportsillustrated.cnn.com/football/college/scoreboards/top25/today/
contains a bunch of iframes with game scores in it. Those iframes refresh every
so often in order to show the latest scores. I noticed that after I left that
page and went to a page on a completely different server, Mozilla was still
contacting sportsillustrated.cnn.com every few seconds. I got the watch cursor
and the status bar said "contacting sportsillustrated.cnn.com." I double checked
that there were absolutely no tabs containing that page still open. Then I
closed the tab that the CNN page had been loaded in. But Mozilla is still
contacting cnn.com every few seconds. A tcpdump shows it GETing URLs like 
http://sportsillustrated.cnn.com/football/college/scoreboards/2002/regularseason/12/1107.exclude.html
every 30 seconds or so. That's the URL of one of the iframes that was on
http://sportsillustrated.cnn.com/football/college/scoreboards/top25/today/

At this point, it's been 20 minutes and Mozilla is still loading those URLs over
and over in the background, with no tab open containing that content. The only
way I can see to make it stop is top quit Mozilla completely.

This is Mozilla 2002110508 on MacOS X 10.2.1.


Reproducible: Didn't try

Steps to Reproduce:
1. Load
http://sportsillustrated.cnn.com/football/college/scoreboards/top25/today/ in a tab
2. Close that tab
3. Watch tcpdump (or similar) for continued loads from sportsillustrated.cnn.com

Comment 1

[Greg K.]

Sean, you indicated you didn't try to reproduce this problem. Please make at
least one attempt to reproduce this problem yourself.

Comment 2

[Sean Harding]

It's actually not true that I didn't try to reproduce it; it's just that I
haven't been able to reproduce it reliably. I've made it happen more than once,
but it doesn't happen every time and I haven't been able to determine what the
common link is between occurrences. I'm still working on that.

(On a tangent, if we're going to be forced to use guided mode to enter bugs now,
it would be really nice to see the interface on that improved. It seems really,
really unweildy to me.)

Comment 3

[Greg K.]

Sean, can you still reproduce this problem using a current nightly build?

Comment 4

[Christian Hamacher]

This looks like a duplicate of bug 194994

Since there hasn't been any communication from the reporter for quite some time,
and since chances are good that this has been fixed by the (temporary) fix in
bug 194994 (which is being kept open for a more thorough fix), I'm marking this
bug a duplicate.

I'm dupe'ing the older bug in this case because bug 194994 has patches and a
solid technical lead on what's happening.

If you disagree this is a dupe, or if you are still seeing this with a current
build, please reopen.

*** This bug has been marked as a duplicate of 194994 ***