3.5.1 blank pages
Mitch Claborn
Periodically, FireFox renders a given page as completely blank. I
refresh, sometimes more than once, and the page renders fine. I compare
the "view source" between a blank page and a good page, and the source
is identical. Any ideas?
Mitch
David McRitchie
Some serious background processing -- whoops on a PC things aren't in the
background everyone grabs until they run out of breath. You probably have
something like an email program or a antivirus program soaking up all the
cycles.
Also check "Problematic Extensions"
http://kb.mozillazine.org/Problematic_extensions
Hector
I've witness this too. I installed 3.5.1 just a few days ago and no
doubt, this package has some stabilities issues. I never had to reboot
(or log off/on XP) more times in the past few days to get things back
to normal.
I have it in the back in my mind that my mixing of 3.5.1 (installed
for testing) and 1.5 usage (my primary browser) may be related,
causing issues in particular with rendering. I had to reboot to get my
rendering back to expectations. I already established that its not a
good idea to run both at the same time. There is obvious sharing of
code somewhere.
Oh well. The bigger/complex you (FF) get, the more problematic it
becomes. No surprise, par for the course for a growing package I
guess. :-)
--
Sincerely
Hector Santos
http://www.santronics.com
Ralph Fox
Mitch Claborn <mi...@claborn.net> wrote:
> Open SuSE 11.1, Firefox 3.5.1
>
> Periodically, FireFox renders a given page as completely blank. I
> refresh, sometimes more than once, and the page renders fine.
Most times when I see this, it is caused by the web server being slow
to respond to me - so my ISP's transparent HTTP proxy times out and
returns me an empty page.
> I compare
> the "view source" between a blank page and a good page, and the source
> is identical.
When you use "view source", Firefox generally re-fetches the page
from the web server. For as real test, you need to put Firefox
into off-line mode before using "view source".
> Any ideas?
>
> Mitch
--
Regards
Ralph
Mitch Claborn
packets, and the final packet of the response arrives in about 8
seconds. That shouldn't be long enough to cause this problem. When I
do the "view source" in offline mode, it still shows the full source
that I expect to see. I'll probably back off to a 3.0.x version and see
if I still have this problem.
Mitch
Ralph Fox
Mitch Claborn <mi...@claborn.net> wrote:
> This was also my first theory, but I've run wireshark to trace the
> packets, and the final packet of the response arrives in about 8
> seconds. That shouldn't be long enough to cause this problem.
I agree. 8 seconds should not cause a problem.
> When I
> do the "view source" in offline mode, it still shows the full source
> that I expect to see. I'll probably back off to a 3.0.x version and see
> if I still have this problem.
I sometimes see pages which don't display properly the first time.
Google Groups is one example -- sometimes the thread tree and
article are cut off halfway down the page. A reload usually fixes.
I suspect that this is a some kind of race condition between arrival
of the HTML and the CSS, and Firefox / Gecko doesn't reflow the page
again when it should.
I've also seen this for all versions of Firefox -- it is not new with 3.5.
--
Regards
Ralph