Closed Bug 141847 Opened 22 years ago Closed 21 years ago

build gets into a state where it won't load certain urls

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
VERIFIED DUPLICATE of bug 123662
Milestone:
Future

People

(Reporter: mikepinkerton, Assigned: darin.moz)

References

Details

(Keywords: regression, Whiteboard: [need testcase]) 

After surfing for a while, the build will get into a state where it won't load
certain urls anymore, such as a google search or a bugzilla query. once it's in
this state, you have to quit the app to get it to query bugzilla again. You get
an error dialog saying:

"the file /show_bug.cgi?id=69566 cannot be found. please check the location and
try again."

when doing a normal bugzilla url. i've been seeing this for the last month, but
haven't been able to track it down to a particular cause. it's pretty stop-ship,
i think since you basically can't use the app anymore once this starts happening.
oops, wrong component
Assignee: Matti → darin
Component: Browser-General → Networking: HTTP
Keywords: mozilla1.0, nsbeta1, regression
QA Contact: imajes-qa → tever
Blocks: 138000
forgot to mention, this is branch. dunno about the trunk. using a 5/1/02 build,
but i've seen it at least as far back as 4/15/02 branch.
short question: Do you used NS6.X and Mozilla at the same time ?

i saw the same thing on OSX with a trunk build after clearing the disk cache.
nope, only the branch build.
I've seen this on trunk for quite some time now (never got around to file a bug,
since it was so unreproducable) (on linux, that is)
this happened to me under windows (here it is windows xp) too.
after some time (its not reproducable) either i can't enter an url into the
url-line or it simply doesn't react when i press enter after entering an url.
let's get something straight, this is different than the "when i hit enter in
the url bar, nothing happens" bug. in this bug, the browser tries to load the
url and produces a dialog saying that the requested url cannot be found.
*** Bug 142673 has been marked as a duplicate of this bug. ***
removing from 138000 list. only drivers add to that tree.
No longer blocks: 138000
reducing severity to major since this is not easily reproducible.  leaving
untargeted since there are no steps to reproduce this bug.
Severity: blocker → major
Whiteboard: [need testcase]
while there aren't any steps to repro, it happens quite a lot for me. One thing
that I was doing the last time it happened was reloading a page over and over
again. Eventually it just stopped working and started giving me the error. See
if that helps repro this.

This is pretty serious. We can't ship a product with a regression such as this.

cc'ing asa who removed this from the moz1.0 blocker list. asa, we need to get
this resolved. a web browser that just craps out after a while isn't that great
of a product.
mike, can you run with HTTP logging enabled, and try to reproduce the problem? 
granted, you'll likely generate a huge log file, but that may be the only way to
determine what's going on here.

  NSPR_LOG_MODULES=nsHttp:5

thx!
mass futuring of untargeted bugs
Target Milestone: --- → Future
adt: nsbeta1-
Keywords: nsbeta1 → nsbeta1-
Mike:

This is pretty old. I had problem on my Mac for a while, mostly in FTP, but it
seems to have gone away.

Is this WorksForYou now?
QA Contact: tever → httpqa
haven't seen it in a while, but that worries me. if we didn't fix it, and others
had the same problem, it could bite us again if we don't understand it.
If you want to leave it open, can we change the summary so it says something
about getting an error dialog? Right now, if someone had this problem as well, I
don't think they could find your bug.
this is a duplicate, and that bug does have a better summary (imho)

it's not mac specific

*** This bug has been marked as a duplicate of 123662 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
VERIFIED/dupe.
thanks.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.