if i keep the webpage(s) open, Firefox will not release the open port when I log off.




14 years ago
13 years ago


(Reporter: dmosullivan, Assigned: darin.moz)


Windows XP

Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2

If i leave firefox web pages open (to read later) and sign off, then i almost
always get the error when trying to dial-up again (with the old pages still
open) that the "port is already open" (even though i have a dial up tone and my
phone line is not in use). The only fix is that Firefox forces me to close all
(old) opened webpages (i.e., close all FireFox windows) before Firefox releases
the open port and allows me to dial-up again. This only happens with Firefox,
and not with IE or Opera. I use a standard Earthlink dialup connection. I like
Firefox much better that IE, but this is such a pain in the ass (having to close
all old windows just to release the open port Firefox insists on hanging on to)
that I'm considering just switching back to IE.

Reproducible: Always

Steps to Reproduce:
1. open 3 or 4 Firefox windows, each with 2 or 3 opened tabbed windows.
2. leave all Firefox windows open, and log off.
3. i try to log back on, but i almost always (but not quite always) get "Port
Already Open" because Firefox refuses to release the open port from step 1 above
unless I close ALL previously open windows from Step 1 above.

Actual Results:  
Can not log back on because "Port Already Open" error message. Firefox refuses
to release the open port from the first logon session, unless I close ALL
previously open windows.

Expected Results:  
Release the previously opened port when you log off, not only when you close the
browser window.

None. Default Settings - using firefox as installed by default download (on a
Windows XP, Dell Pentium machine).

Comment 1

14 years ago
Reporter: Can you please try with Firefox 1.0.1?  Your bug may have been fixed
since then.

-> Core: Networking
Assignee: firefox → darin
Component: General → Networking
Product: Firefox → Core
QA Contact: general → benc
Version: unspecified → Trunk
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.