Closed Bug 226613 Opened 21 years ago Closed 19 years ago

Connectivity stops working

Categories

(Core :: Networking: HTTP, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: ChocolateCheeseCake, Assigned: darin.moz)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6b) Gecko/20031123 Firebird/0.7+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6b) Gecko/20031123 Firebird/0.7+

Visited http://www.osnews.com and viewed the a page for around 5minutes, then
proceeded to post a reply and the the browser informs me that it can't connect
to the website. I then proceeded to continually click and press enter to clear
the error message until it suddenly worked.

This has only started since the the nightlies have been based on the 1.6 series.
The error also occurs on Camino and Mozilla nightlies as well.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
> The error also occurs on Camino and Mozilla nightlies as well.

Shifting over to Browser.
Component: General → Networking: HTTP
Product: Firebird → Browser
Version: unspecified → Trunk
.
Assignee: blake → darin
QA Contact: httpqa
bz,

Sorry about that, I forgot to shift owner/QA.
When the problem occurs I ping an address and the error is returned "Bus error". This only started 
in the nightlies based on 1.6 trunk.
I've just checked out Mozilla 1.5.1 and the problem hasn't cropped up in that.
The most likely senario is a problem with the resolving code what was tweaked in
the 1.6 trunk.
HELLO! is this bug going to be fixed or is it being ignored?
No one is purposefully ignoring your bug. The fact of the matter is that there
are a LOT of open bugs, and not all of them can be fixed immediately. Comments
like yours don't expedite the process.
ChocolateCheeseCake, can you reproduce the problem using a new user profile?
<i>------- Additional Comment #8 From Greg Kolanek (let's re-adopt MNG+JNG) 
2003-12-06 04:20 ------- 
ChocolateCheeseCake, can you reproduce the problem using a new user profile?</i>

Yes, this is reproducable. Unfortuntely this problem only occurs on MacOS 
10.2.8. I haven't tested 10.3, however, I have heard that the problem doesn't 
exist there. I see that Firebird is compiled on a machine running 10.2.8 where 
as Mozilla still uses an older version. Maybe if the tinderbox was upgraded to 
10.2.8 what it is it now, which appears to be 10.2.6, maybe that will fix the 
problem?
Just using Mozilla 1.6B right now and it appears that the issue only effects
MacOS X 10.2.x series and not 10.3.x
WFM using OSX 10.3.2, Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
rv:1.7a) Gecko/20040123
I believe this may have been fixed in bug 240759.

Please try Mozilla 1.7 RC1 or later. Does that solve the problem?
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.