#3106: Checking with large hash size causes OOM condition
-----------------------+----------------------------
Reporter: bittaurus | Owner:
Type: bug | Status: new
Priority: critical | Milestone: needs verified
Component: Core | Version: 1.3.15
Keywords: |
-----------------------+----------------------------
{{{
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.
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/3106>
Deluge <http://deluge-torrent.org/>
Deluge Project
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/deluge-dev.
For more options, visit https://groups.google.com/d/optout.
