Opened 13 years ago
Closed 13 years ago
#2691 closed Bug (fixed)
socket limit has a wrong value
| Reported by: | tiennou | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | Transmission | Version: | 1.76+ |
| Severity: | Normal | Keywords: | |
| Cc: |
Description
It's been 4 days I'm looking at Transmission which is open and does nothing, tough there are lots of peers available.
Today I launched it under Xcode, and I found this while checking tr_fdSocketCreate :
p gFd->socketLimit $2 = -513
I'm wondering how this could have happened, but maybe resetting it to a sane value would help some users ;-). I don't have any more information about how it ended up being negative, but the results are painfully visible...
Change History (2)
comment:1 Changed 13 years ago by tiennou
comment:2 Changed 13 years ago by livings124
- Milestone None Set deleted
- Resolution set to fixed
- Status changed from new to closed
Thanks! r9809
Note: See
TracTickets for help on using
tickets.
It seems the problem lies in clamp(), which takes int parameters while struct rlimit is made of two uint64_t on OS X. Changing clamp declaration to long clamp( long val, long lo, long hi ) fixes the problem.