Comment 20 for bug 639659

Ok. Thanks.

Message from libtorrent author:
***
could somebody that experience this run a heap profile? google-performance tools are good for this for instance.

You can inject tcmalloc when starting qBittorrent or Deluge, specify to enable heap profiling and go. Generate a report with pprof and one of the heap files from when libtorrent started using a ton of memory and attach it here.

See: http://google-perftools.googlecode.com/svn/trunk/doc/heapprofile.html
***