471758 - Incorrect rendering of pages - css does not seem to be parsed, images not loaded

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[grahamveal]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-GB; rv:1.9.0.5) Gecko/2008120121 Firefox/3.0.5
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-GB; rv:1.9.0.5) Gecko/2008120121 Firefox/3.0.5

This does not seem to be an easily reproducable problem. But has happened probably twice a week. When browsing around, all is woring well, and then all of a sudden the rendering of the pages seems to break. Once this happens I go back to google (which seems to look ok), then I do a search, click on a search result and nothing happens. Well, the little spinner shows for a split second, but I am still on the search results page. I then click my home button (google) and then do the search again, still cannot click the links. So I do a few refreshes and then I seem to be able to click the link. Again, this this is not an exact science to get it to work. Then I go to my page and the page is not rendered correctly. The CSS does not seem to be parsed and applied, and some images are not displayed. I then try another site and it does not work. So back to google again, do another search and seems some pages start working. But another website down, and the display has gone again. Now I have left the browser open for about 10 minutes, doing nothing, and all seems to be fine? I realise this is going to be hard to reproduce, so I think I should say about how I use my MacBook. I generally do not switch it off, maybe it gets restarted once a week or two. I usually, just close the screen and let it go to sleep, then just open it up, wait for airport to reconnect and start browsing. I can only think that this could be related to how OSX handles going to sleep. But it is weird, how leaving the browser for around 10 minutes seemed to solve the issue? Otherwise, I quit FireFox and restart which solves the problem.

Reproducible: Sometimes

Steps to Reproduce:
1.
2.
3.

Comment 1

[grahamveal]

Attachment: Screen shot of broken site

Comment 2

[grahamveal]

Attachment: Another screen shot

Comment 3

[grahamveal]

Attachment: And another

Comment 4

[Ria Klaassen (not reading all bugmail)]

Could this be Bug 449357 ?

Comment 5

[Tyler Downer [He/Him]]

Because you are restarting, it seems like it could be a extension. Try in Safe Mode.

Comment 6

[grahamveal]

I have been trying it in safe mode, and with all my plugins disabled. It still keeps on hapening. Being a developer myself I really want to be able to give you steps to reproduce it, but I can't. It just seems to happen after using the browser for a while. If you need any more info about my setup, please let me know.

Comment 7

[cmtalbert]

(In reply to comment #4)
> Could this be Bug 449357 ?

This does look to be the same issue, and grahamveal can reproduce it in safe mode. What's unusual is that I have exactly the same browsing behavior as you do - never shutting down the browser, only restarting the machine every couple of weeks but I've never seen this.

I'm not sure what we can do here without a reproducible case. Grahamveal, can you tell us if there were any errors in the Error Console when this occurs?

Comment 8

[grahamveal]

When it happens again, i'll check the error console, and let you know. We have been trying to see if it is possibly the same website that keeps making the issue occur, and it seems to happen most times when my fiance is browsing http://www.thesun.co.uk/

Comment 9

[grahamveal]

It has just happened again. I opened a new tab and clicked the home button (google), but it wouldn't load a page. It shows the loading spinner for a spit second, then it just has the title '(Untitled)'. I managed to open the error console, althogh for my fiance it wouldn't even show it? Here is the message:

Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFileOutputStream.init]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: file:///Applications/Firefox.app/Contents/MacOS/components/nsSessionStore.js :: sss_writeFile :: line 2166"  data: no]
Source File: file:///Applications/Firefox.app/Contents/MacOS/components/nsSessionStore.js
Line: 2166

There were some other general messages, but they were just css and js warnings.
Firefox wouldn't let me quit, I clicked the red x, the button went to it's 'clicked' state, but just stayed like that. This seems to be a bit worse than before, so not sure if it is completly related?

Comment 10

[Mike Wood]

This exact problem has been happening to me for a long time. It happened when I was using a ppc and it is happening now that I am using Intel. It seems completely random and I am also a software developer so it is very frustrating to not be able to find something reliable that might be triggering the problem. The symptoms as described here happen for me as well. Pages will not format correctly, may not load all or any of the pictures, a refresh rarely works but most of the time simply makes the page load incorrectly in a different way, clicking links does not seem to register a click, can't search in google, and can't close or quit Firefox. The only way to quit is to right-click the icon and quit from there. Restarting the browser might fix it for an hour or 30 seconds.

This seems to be the same as 449357.

Comment 11

[Tyler Downer [He/Him]]

This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.

Comment 12

[Tyler Downer [He/Him]]

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.

Comment 13

[grahamveal]

Not present in current version