Opened 13 years ago

Closed 13 years ago

#1799 closed Bug (worksforme)

"too many open files" 1.42+

Reported by: btrr Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 1.42
Severity: Normal Keywords:


I have searched, and this appears different from the other bugs relating to "too many open files" error.

had to quit using 1.42 because of a frequent crasher unfortunately, 1.42+ versions rarely start properly for me, there are a number of odd problems related to "too many files". sometimes I get this: (transmission:8457): Pango-WARNING : error opening config file '/etc/pango/pangorc': Too many open files which results in no fonts, but otherwise apparently functional... other times it will fail to open a bunch of .torrent files, resulting in disappearing/stuck torrents and other weirdness. and sometimes it just wont open icons... in any case, pretty broken, and I think I will have to compile 1.42 with the patch for the 1 crasher, or attempt to switch back to [trusty-but-not-so-lightweight-client-which-can-also-move-completed-files] because I really cant figure this out... after starting 1.5b3 / current svn a few times, the total number of torrents dropped several times, as it appears it would not try to start those ones again. even at half the full number of loaded torrents, the problems persisted. switching back to 1.42, none of these problems exist, but it will soon crash.

I am on ubuntu 8.10 amd64. I have checked ulimits, and increased them. file limit is at 32768. I do have over 1000 torrents in the client, but many are paused, and I have low connection limits, so I dont actually see transmission opening more than 300 files in reality at the very most (using 'lsof -p pidof transmission | wc -l') (... actually that includes sockets too, cant remember the other lsof switch right now, but more like half, in any case, much less than 1024, or 32768 or whatever), and when it works, it works great with very little burden.

have been using gtk client, but have tried switching to the daemon, and was still affected by these issues.

I do not remember when I first saw this. maybe a month or so ago, when I first had trouble with 1.42.

Change History (5)

comment:1 Changed 13 years ago by btrr

sorry about some text... anyway, still seeing this in current builds, reverting to (patched) 1.42. let me know if there is any way I might help improve upcoming version.

comment:2 Changed 13 years ago by charles

This may be related to #1810. If so, 1.50b6 should solve the problem, so could you give it (or the upcoming 1.50) a spin and see if the problem persists?

comment:3 Changed 13 years ago by charles

  • Version changed from 1.42+ to 1.42

comment:4 Changed 13 years ago by livings124

btrr: ping

comment:5 Changed 13 years ago by livings124

  • Resolution set to worksforme
  • Status changed from new to closed

Please reopen if this is still an issue.

Note: See TracTickets for help on using tickets.