Closed Bug 1258836 Opened 8 years ago Closed 8 years ago

nsSocketTransportService::gMaxCount is hard-coded to a too small value on linux/OS X

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: bwc, Unassigned)

References

Details

Right now the limit is 50 sockets on either OS X or linux. This is causing intermittent failures on the tests over in bug 1231975, because those tests chew up lots of sockets simulating port-dependent NATs. We either need this number to be larger, or some way to tweak it at runtime. 50 seems low to me for ordinary usage, to be honest.
50 is the absolute minimum number.. osx and linux do some getrusage() calls to try and get a higher number.

is that not working for you? My linux desktop is reporting 550 (which is the cap).

or maybe you meant 550 is too low? (its old and historical.. so sure, plausible.)
Hmm, I read the code wrong it seems. Let me try something.
Ok, I've found the problem I think, the current limit should be fine.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.