254272 - winsock error "no buffer space available" not handled

Status: RESOLVED EXPIRED

(Core :: Networking, defect)

Description

[Andrei Boros]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2

Having other applications starve Windows of network resources such that
attempting to open a new TCP connection results in the Winsock error "No buffer
space available", Thunderbird (tested 0.7.1) does not handle this error properly.



Reproducible: Always
Steps to Reproduce:
1.use several bittorent clients until windows is starved of network resources
2.have a configured mail account (eg a POP3 account), try to get mail
3.

Actual Results:  
Nothing really happens. 
Pressing "get mail", in the status bar says "Connecting to [...]" and remains
like this. 


Expected Results:  
Should display an error dialog with the proper error string, something like this : 
TCP error : "No buffer space available"


Tested on windows98, I assume it's valid for all windows platforms, only the
ease of reproductibility of the error may change as 2k or XP may have more
network resources. 
I can reproduce the error having about 5 bittorrent downloads, each connected
with 10-30 peers, and wait till windows gets starved. 

My suggestion is an improvement in the winsock error handler, such that
thunderbird is able to properly report a meaningful error number and error string.

Not tested for the same problem when contacting a SMTP server, but I will add
details about it as soon as I can test it.

Comment 1

[Andrei Boros]

Tested same situation in the case of sending mail.
When attemtping to contact the SMTP server, under the same conditions, a generic
error dialog box is displayed (error connecting to the SMTP server, connection
refused or SMTP server is unavailable...)

So, in case of SMTP, the error is somewhat handled (though not explicitely enough)

Comment 2

[Jason Bassford]

*** Bug 254270 has been marked as a duplicate of this bug. ***

Comment 3

[Owen Marshall (Not reading bugmail)]

Over to Necko.

Comment 4

[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 5

[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.