Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

The tool "Report a broken website" doesn't work. Need to submit a report with screenshots.

  • 4 பதிலளிப்புகள்
  • 1 இந்த பிரச்சனை உள்ளது
  • 2 views
  • Last reply by Jon_Roland

Jon_Roland
Jon_Roland
more options

Example of problem on http://constitution.org/rror/rror--00.htm

iframe content often displayed in the wrong places, or sometimes not at all. Similar problem with other pages on site. Pages display correctly with IE, Google Chrome, Safari, and sometimes in Firefrox as well, especially just after a new start, so the problem is not the underlying HTML, and the fact that Firefox usually does initially display it correctly, but fails to do so after running a while, suggests something like a memory leak.

Using Firefox v. 3.6.23 Linux under Fedora.

Example of problem on http://constitution.org/rror/rror--00.htm iframe content often displayed in the wrong places, or sometimes not at all. Similar problem with other pages on site. Pages display correctly with IE, Google Chrome, Safari, and sometimes in Firefrox as well, especially just after a new start, so the problem is not the underlying HTML, and the fact that Firefox usually does initially display it correctly, but fails to do so after running a while, suggests something like a memory leak. Using Firefox v. 3.6.23 Linux under Fedora.

All Replies (4)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Clear the cache and the cookies from sites that cause problems.

"Clear the Cache":

  • Edit > Preferences > Advanced > Network > Offline Storage (Cache): "Clear Now"

"Remove Cookies" from sites causing problems:

  • Edit > Preferences > Privacy > Cookies: "Show Cookies"

Did you make changes to network.http prefs of have enabled HTTP pipelining?

Jon_Roland
Jon_Roland கேள்வியின் உரிமையாளர்
more options

I had already tried clearing everything, which didn't work. Just tried changing the network.http.pipelining value to true in prefs.js by entering about:config in the location field of the browser, and rebooted the system. That seems to work, for now, but rebooting the system has worked before -- for a while. It should not be necessary to have to frequently reboot to avoid the problem. For that matter, it should not be necessary to have to edit the prefs.js file. Other browsers seem to work without having to do that.

Jon_Roland
Jon_Roland கேள்வியின் உரிமையாளர்
more options

Okay, problem has returned. It is not fixed by settings or clearing everything. Seems to come from running too long, which, as I said before, suggests a memory leak.

Jon_Roland
Jon_Roland கேள்வியின் உரிமையாளர்
more options

One further problem, wh8ich may or may not be connected. For some time now I have been unable to just close Firefox and re-open it again without first killing a lingering firefox process in the shell that doesn't get closed by closing the window, and prevents re-opening. Since the problem appeared about the same time, I have to wonder if the two problems have a common origin.