450281 - Pages keep reloading and never fully load

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[Rick]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1

Several websites exhibit this problem usually from a link within the site to subsequent pages. this does not occur if i visit using another browser. The problem also occurs when firefox is trying to open a large pdf file into a new tab.
The problem does not occur at all times at the same url, sometimes the page loads correctly.
The status bar alternates between contacting site and stopped.

Reproducible: Sometimes

Steps to Reproduce:
1.try opening link to showtimes from www.showcasecinemas.co.uk
2.
3.
Actual Results:  
Problem occurred twice then didn't occur the following morning but didn't happen using windows IE

Comment 1

[Tyler Downer [He/Him]]

The issue being that the pages refresh over and over again?

Comment 2

[Rick]

(In reply to comment #1)
> The issue being that the pages refresh over and over again?
> No they never seem to fully load. I have had pages refresh after loading but then they seem stable so I assume that someone else will report that and a fix will be found

Comment 3

[Tyler Downer [He/Him]]

What pages are these? Have you tried to reproduce this in Safe Mode?

Comment 4

[Bill Gianopoulos [:WG9s]]

I was having this issue and determined, in my case at least, that it was caused by the Favicon Picker 3 extension, which appears to be incompatible with the current trunk.  Not only does it cause this issue, but it also logs errors in the error console:

Warning: Warning: Ignoring unrecognized chrome manifest instruction.
Source file: file:///home/wag/.mozilla/firefox/o14rqv99.default/extensions/%7B446c03e0-2c35-11db-a98b-0800200c9a67%7D/chrome.manifest
Line: 7

Line 7 is:
//override chrome://browser/content/places/menu.xml chrome://faviconpicker/content/menu.xml

Warning: Warning: Ignoring unrecognized chrome manifest instruction.
Source file: file:///home/wag/.mozilla/firefox/o14rqv99.default/extensions/%7B446c03e0-2c35-11db-a98b-0800200c9a67%7D/chrome.manifest
Line: 8

Line 8 is:
//override chrome://browser/content/places/toolbar.xml chrome://faviconpicker/content/toolbar.xml

Warning: Warning: Ignoring unrecognized chrome manifest instruction.
Source file: file:///home/wag/.mozilla/firefox/o14rqv99.default/extensions/%7B446c03e0-2c35-11db-a98b-0800200c9a67%7D/chrome.manifest
Line: 9

Line 9 is:
//override chrome://browser/content/places/utils.js chrome://faviconpicker/content/utils.js

Comment 5

[Rick]

(In reply to comment #4)
Thanks Bill I don't have that extension but I do have a couple of others which I will remove and try again. If that doesn't work I think I'll uninstall and try with a clean install.

> I was having this issue and determined, in my case at least, that it was caused
> by the Favicon Picker 3 extension, which appears to be incompatible with the
> current trunk.  Not only does it cause this issue, but it also logs errors in
> the error console:
> 
> Warning: Warning: Ignoring unrecognized chrome manifest instruction.
> Source file:
> file:///home/wag/.mozilla/firefox/o14rqv99.default/extensions/%7B446c03e0-2c35-11db-a98b-0800200c9a67%7D/chrome.manifest
> Line: 7
> 
> Line 7 is:
> //override chrome://browser/content/places/menu.xml
> chrome://faviconpicker/content/menu.xml
> 
> Warning: Warning: Ignoring unrecognized chrome manifest instruction.
> Source file:
> file:///home/wag/.mozilla/firefox/o14rqv99.default/extensions/%7B446c03e0-2c35-11db-a98b-0800200c9a67%7D/chrome.manifest
> Line: 8
> 
> Line 8 is:
> //override chrome://browser/content/places/toolbar.xml
> chrome://faviconpicker/content/toolbar.xml
> 
> Warning: Warning: Ignoring unrecognized chrome manifest instruction.
> Source file:
> file:///home/wag/.mozilla/firefox/o14rqv99.default/extensions/%7B446c03e0-2c35-11db-a98b-0800200c9a67%7D/chrome.manifest
> Line: 9
> 
> Line 9 is:
> //override chrome://browser/content/places/utils.js
> chrome://faviconpicker/content/utils.js
> 

Comment 6

[Rick]

After uninstalling all extensions the problem seems fixed but I haven't re-instlled any yet so it may re-occur when I do.
Many thanks to all who suggested fixes.


(In reply to comment #5)
> (In reply to comment #4)
> Thanks Bill I don't have that extension but I do have a couple of others which
> I will remove and try again. If that doesn't work I think I'll uninstall and
> try with a clean install.
> 
> > I was having this issue and determined, in my case at least, that it was caused
> > by the Favicon Picker 3 extension, which appears to be incompatible with the
> > current trunk.  Not only does it cause this issue, but it also logs errors in
> > the error console:
> > 
> > Warning: Warning: Ignoring unrecognized chrome manifest instruction.
> > Source file:
> > file:///home/wag/.mozilla/firefox/o14rqv99.default/extensions/%7B446c03e0-2c35-11db-a98b-0800200c9a67%7D/chrome.manifest
> > Line: 7
> > 
> > Line 7 is:
> > //override chrome://browser/content/places/menu.xml
> > chrome://faviconpicker/content/menu.xml
> > 
> > Warning: Warning: Ignoring unrecognized chrome manifest instruction.
> > Source file:
> > file:///home/wag/.mozilla/firefox/o14rqv99.default/extensions/%7B446c03e0-2c35-11db-a98b-0800200c9a67%7D/chrome.manifest
> > Line: 8
> > 
> > Line 8 is:
> > //override chrome://browser/content/places/toolbar.xml
> > chrome://faviconpicker/content/toolbar.xml
> > 
> > Warning: Warning: Ignoring unrecognized chrome manifest instruction.
> > Source file:
> > file:///home/wag/.mozilla/firefox/o14rqv99.default/extensions/%7B446c03e0-2c35-11db-a98b-0800200c9a67%7D/chrome.manifest
> > Line: 9
> > 
> > Line 9 is:
> > //override chrome://browser/content/places/utils.js
> > chrome://faviconpicker/content/utils.js
> >

Comment 7

[Tyler Downer [He/Him]]

This is a technical bug reporting database, and so FIXED is for patches that are checked into the tree. Please use INVALID. If you find the extension that is causing this issue, contact the developer of that extension.