Daemon not updating trackers on exit

[ludwig]

Hi. I've just started using Deluge and can't seem to stop the daemon gracefully. When I send SIGTERM to the daemon process it exists in less than a second and the trackers are not updated (they show me as a seeder after terminating the daemon). The same happens with the GTK GUI option "Quit & Shutdown daemon". It is a bit annoying to have to stop the torrents manually before shutdown.

My setup:
Gentoo "unstable" branch, kernel 3.10.10
Deluge 1.3.6
libtorrent 0.16.11
Dependencies: dev-python/setuptools-1.1.5, dev-util/intltool-0.50.2, dev-python/chardet-2.0.1, dev-python/pyopenssl-0.13.1, dev-python/pyxdg-0.25, dev-lang/python-2.7, dev-python/twisted-core-13.0.0, dev-python/twisted-web-13.0.0, dev-libs/geoip-1.5.1, dev-python/pygobject-2.28.6, dev-python/pygtk-2.24.0, gnome-base/librsvg-2.37.0, dev-libs/boost-1.53.0, sys-devel/libtool-2.4.2, sys-libs/zlib-1.2.8, dev-libs/openssl-1.0.1e

Deluge is handling ~400 torrents on a 100/10 connection.

The LOG says:
[INFO ] 17:08:38 daemon:187 Waiting for components to shutdown..
[DEBUG ] 17:08:38 core:146 Core stopping...
[DEBUG ] 17:08:38 torrentmanager:696 Saving torrent state file.
[INFO ] 17:08:38 rpcserver:223 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO ] 17:08:38 daemon:187 Waiting for components to shutdown..

Any ideas on what can be wrong and how to fix it?

[ludwig]

I found another problem that may be related to this issue. If I select a bunch of torrents and pause them, only some of them are stopped properly (for example, 46 torrents stopped correctly out of 214). Stopping of 200+ torrents should take some time to avoid hammering the trackers. It just takes one second in Deluge. It looks like Deluge (or libtorrent) does this in a very aggressive way and the trackers may be dropping some of the messages.

Anyone else noticed this issues? Shoul I talk about this here or open a bug report?

[Cas]

I am not aware of anything that Deluge can do differently, you need to talk to the libtorrent developer about this, the libtorrent sourceforge mailing list is the usual place or IRC if you are lucky.