Total byte control !

[sledgehammer_999]

@switeck and @nico910 totally offtopic: But since you're using Gbps connections you be aware of another limitation of libtorrent(even 1.0.x): https://code.google.com/p/libtorrent/is ... &start=100

@nico910 I found an easy tool to use for profiling. Copy qbittorrent.exe and qbittorrent.pdb inside its folder. You call it using "Heapy_Win32.exe qbittorrent.exe". Run qbt with 1400MiB until it craches. Try to produce the crash twice. Each time rename the created file named "Heapy_Profile.txt" to something else before running the second test, otherwise it will append the results in the same file.
Download the zip: http://lukedodd.com/projects/Heapy%20Version%200.1.zip
Heapy github repo: https://github.com/lukedodd/Heapy

[nico910]

I never had any problem with cpu, plus i'm encoding 24/24 videos to h.265 with medium preset and i don't have any core at 100%
the problem should depend of the cpu used.

ok i'll try this tool

first crash (The message exceeds the maximum allowed length (80000 characters).
http://pastebin.com/uzwP1RKh

second crash (occured at 1909.5MB)
http://pastebin.com/Cek2vEwC

[sledgehammer_999]

@nico910 mention in the libtorrent bug what cache setting you were using. I forgot to add it to my comment.