Checking with large hash size causes OOM condition

[bittaurus]

Gentoo Base System release 2.3
DISTRIB_ID="Gentoo"

Linux host 4.9.20-hardened-host-r1 #2 SMP Sun Apr 9 10:02:56 2017 x86_64 Intel(R) Pentium(R) CPU G850 @ 2.90GHz GenuineIntel GNU/Linux

MemTotal:        8123444 kB

Running deluged in server/client mode.

I created a .torrent file from a 14G dataset using mktorrent -l 28. When I attempt to check the hash on this dataset, deluged will chew up memory to about 52%, when it then runs out and my kernel OOM killer shuts down deluged.

This could cause issues after downloading such a set and attempting to recheck.