503550 - uPortal fails first render after clearing Cache & Active Logins and restarting firefox

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Arlo White]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.1pre) Gecko/20090701 Ubuntu/9.04 (jaunty) Shiretoko/3.5.1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.1pre) Gecko/20090701 Ubuntu/9.04 (jaunty) Shiretoko/3.5.1pre

This is a very picky issue but I thought it might be indicative of a caching bug with Firefox. Our campus runs an instance of uPortal. Occasionally when I login the portal doesn't render at all and instead I see a screen filled with the theme background color. If I view source I see the correct html content. Clicking refresh will render correctly.

Reproducible: Always

Steps to Reproduce:
I was able to get this to happen every time by doing the following:
1. Clear Recent History
2. Select Everything
3. Check Cache & Active Logins
4. Clear Now
5. Close all Firefox windows
6. Start Firefox
7. Login to my.calpoly.edu

Actual Results:  
Portal doesn't render, the screen is filled with the page background color.

Expected Results:  
A normal render.

I'm using Ubuntu's firefox-3.5 package.

Comment 1

[Arlo White]

Note that this only happens when I cleared both the Cache AND Active Logins. Clearing just the cache or just Active Logins and restarting didn't cause this issue.

Comment 2

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.12 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Also, please consider using the most recent Firefox 4 beta build, your bug may be resolved there.

Comment 3

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.13 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.