273180 - Browser requires two requests to display many pages.

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Bob Jacobson]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040910
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040910

Frequently (as much as 50% of the time), the browser looks for but cannot find
the target URL and reports back with a "could not find" message.  

After clicking on on the Repeat button, the browser then discovers the page.

I thought this was a problem peculiar to the 1.8.5beta, which I was using.  So I
reinstalled 1.7.3, but the same problem is occurring.

Reproducible: Sometimes
Steps to Reproduce:
1. Enter URL in Address Bar box.
2. Hit RETURN to find URL
3. Browser looks, then times out and reports "could not find" the website.
4. Click on Repeat button and browser finds the URL.

Actual Results:  
Usually, the browser finds and properly displays the intended webpage.

Expected Results:  
The browser should have found the webpage in the first place.

This problem occurs on different networks, so it's not a network problem (so far
as I can tell).

I'm running Mac OS 10.3.6 on a G4/15 Powerbook.

I may be inventing this, but it seems this problem began when I installted the
1.8 beta.  However, even after reinstalling 1.7.3, it's still occuring.  Did the
beta leave something behind?

Comment 1

[Boris Zbarsky [:bzbarsky]]

This could be caused by a corrupt cache... can you make a backup of your cache,
then clear it and see whether that helps?

Comment 2

[Andrew Schultz]

Bob: is this still a problem?  can you try Boris' suggestion?

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.