532845 - After session restore the stylesheet CSS is often not loaded from AMO

Status: RESOLVED WORKSFORME

(Firefox :: Session Restore, defect)

Description

[karl155]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5
Build Identifier: 

Hi, I don't know if its a bug in AMO, but I often see that the stylesheet is not loaded after using session restore in Firefox.
(All images get blue borders and so on.)

AMO seems to be the only page with this problem. I have many other tabs, all get restored correctly.

Reproducible: Sometimes

Steps to Reproduce:
1. Wait until Firefox crashes
2. Restore Tabs
3. Look at the restored AMO page
Actual Results:  
The background is white, the font face is standard, images have blue borders, the positions are completely wrong... Just everything what happens when the stylesheet does not load.

Expected Results:  
Get the correct style.

Comment 1

[Jeff Balogh (:jbalogh)]

(In reply to comment #0) 
> Steps to Reproduce:
> 1. Wait until Firefox crashes

Can we throw this one over the fence to the Firefox people? ;)

Comment 2

[timeless]

i think nspr logging for http/cache would probably be good (for lazy purposes, try setting NSPR_LOG_MODULES=all:5 and NSPR_LOG_FILE=%temp%\nspr.log in a command prompt and running firefox from there).

Comment 3

[karl155]

Shall I do the logging after crashing or before?

(The crash is some memory thing. Firefox eats up all memory and crashes. This happens every few days since 3.5.2 or 3.5.3. But I don't think that this is relevant in this bug, because AMO is the only page which isn't restored correctly.)

Comment 4

[Fred Wenzel [:wenzel]]

fwiw, if you need to crash Firefox, you can use the crashme extension: http://code.google.com/p/crashme/

Comment 5

[timeless]

let's assume it's sufficient to log only the second session, i.e. crash first, then run command prompt, set the env vars, run firefox from there and restore your session.

Comment 6

[Justin Scott [:fligtar]]

Please send this back to AMO if the cause is determined to be something the something in the website that we can fix.

Comment 7

[karl155]

Unfortunately the log is 95 MB big.

This time the error was a little bit different:
- "Dieses Add-on weiterempfehlen" was permanently open
- The title of the addon was below the menu
- "Bewertung" was a drop-down menu with many "*" chars in it

Does anybody know for what I have to search the log? Then I could post the relevant snippet.

Comment 8

[karl155]

Another try, this time I just restarted Firefox (without crashing):

Fehler: Verbindung unterbrochen
Die Verbindung zum Server wurde zurückgesetzt, während die Seite geladen wurde.

(and again, AMO is the only page producing such errors)

Comment 9

[Wayne Mery (:wsmwk)]

the issue you see can happen if your network (ISP, wireless router, etc) doesn't supply css info fast enough. especially when loading lots of pages at the same time which can overload your network. see bug 475603.

does this sound like possible cause of your problem?

Comment 10

[karl155]

I don't think so. Bug 475603 is mainly about DNS errors. But on AMO the stylesheets are loaded from the same Domain as the document (the html page) itself. So if it would be a DNS problem, I would get the "Address not found" error instead of the document with no stylesheet.

My network/Internet connection is really fast too. I don't think that this is the bottleneck. If it would be the problem, I also would see this error on other pages. But I only can see this error on AMO.

Comment 11

[Wayne Mery (:wsmwk)]

DNS errors don't manifest necessarily as strictly hard errors, it can be (as in the case of bug 475603) poor performance. And speed of network isn't the issue - the issue is throughput, i.e. effective speed under specific conditions.

But happening only on AMO is interesting. Can you get the log as described by timeless in comment 2?

Comment 12

[karl155]

I have made one, but that was 95 MB big. Maybe you have something I can "grep" or so. I cannot imagine that anybody wants to read 95 MB of text.

Comment 13

[Wayne Mery (:wsmwk)]

karl, do you still see this?

Comment 14

[karl155]

I did not have AMO open the last time but I still saw this very long time after opening this report.

Comment 15

[karl155]

Can't reproduce this anymore. Maybe the underlying bug is now covered by delayed tab restoring or completely gone. I still have the logs described above.
Marking WFM.