Opened 9 years ago

Closed 9 years ago

#5327 closed Bug (invalid)

Crash when global limit is more than 900

Reported by: lislee2001 Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 2.77
Severity: Normal Keywords:
Cc:

Description

As title, if I set the global limit more than 900, the transmission is very easy to crash. I do not know where does it crash. Is there any way to debug? I hacked my system limit to 8192, and the default is 1024

here is my config file: {

"alt-speed-down": 50, "alt-speed-enabled": false, "alt-speed-time-begin": 540, "alt-speed-time-day": 127, "alt-speed-time-enabled": false, "alt-speed-time-end": 1020, "alt-speed-up": 50, "bind-address-ipv4": "0.0.0.0", "bind-address-ipv6": "::", "blocklist-enabled": false, "blocklist-url": "http://www.example.com/blocklist", "cache-size-mb": 384, "dht-enabled": false, "download-dir": "/home/lzw/transmission/completed", "download-limit": 100, "download-limit-enabled": 0, "download-queue-enabled": true, "download-queue-size": 50, "encryption": 1, "idle-seeding-limit": 30, "idle-seeding-limit-enabled": false, "incomplete-dir": "/home/lzw/transmission/incomplete", "incomplete-dir-enabled": true, "lpd-enabled": false, "max-peers-global": 8192, "message-level": 2, "peer-congestion-algorithm": "", "peer-limit-global": 8192, "peer-limit-per-torrent": 500, "peer-port": 51413, "peer-port-random-high": 65535, "peer-port-random-low": 49152, "peer-port-random-on-start": false, "peer-socket-tos": "default", "pex-enabled": false, "port-forwarding-enabled": false, "preallocation": 1, "prefetch-enabled": 1, "queue-stalled-enabled": false, "queue-stalled-minutes": 30, "ratio-limit": 2, "ratio-limit-enabled": false, "rename-partial-files": true, "rpc-authentication-required": true, "rpc-bind-address": "0.0.0.0", "rpc-enabled": true, "rpc-password": "test123test", "rpc-port": 9111, "rpc-url": "/transmission/", "rpc-username": "test", "rpc-whitelist": "127.0.0.1, *.*.*.*", "rpc-whitelist-enabled": true, "scrape-paused-torrents-enabled": true, "script-torrent-done-enabled": false, "script-torrent-done-filename": "", "seed-queue-enabled": false, "seed-queue-size": 10, "speed-limit-down": 100, "speed-limit-down-enabled": false, "speed-limit-up": 100, "speed-limit-up-enabled": false, "start-added-torrents": true, "trash-original-torrent-files": false, "umask": 18, "upload-limit": 100, "upload-limit-enabled": 0, "upload-slots-per-torrent": 500, "utp-enabled": true, "watch-dir": "/home/lzw/rtorrent/session/", "watch-dir-enabled": true

}

one more question, what is difference between "peer-limit-global" and "max-peers-global"??

Change History (6)

comment:1 Changed 9 years ago by x190

https://trac.transmissionbt.com/wiki/EditConfigFiles#Peers

peer-limit-global: Number (default = 240)

1024 is the hard-coded limit and includes all open files for the process, so never set this value to more than ~800. See the wiki for the proper key names.

For the crash, you would need to produce a backtrace (gdb) or a crash report.

comment:2 Changed 9 years ago by lislee2001

  • Summary changed from Crash when peer is more than global limit is more than 900 to Crash when global limit is more than 900

comment:3 Changed 9 years ago by jordan

lislee2001, what OS are you running Transmission on?

If you're on an OS with automatic bug reporting like Ubuntu or Fedora, best to let their tools generate the crash report by you filing a bug on their respective bug trackers.

Otherwise, as x190 says you'll need to get a gdb backtrace by hand. :/

comment:4 follow-up: Changed 9 years ago by lislee2001

I am using Ubutu12.04.

BTW, how to generate bug report with 12.04?

comment:5 in reply to: ↑ 4 Changed 9 years ago by x190

Replying to lislee2001:

I am using Ubutu12.04.

BTW, how to generate bug report with 12.04?

https://help.ubuntu.com/community/ReportingBugs

comment:6 Changed 9 years ago by jordan

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

lislee2001:

In 12.04 you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Note: See TracTickets for help on using tickets.