Opened 6 years ago

Closed 6 years ago

#1869 closed bug (Fixed)

Memory problems with Deluge and libtorrent v0.15 on Windows

Reported by: xzilvinas Owned by: andar
Priority: major Milestone: 1.3.3
Component: Windows OS Version: 1.3.2
Keywords: Cc:

Description

Well this bugs occurs when I add torrent and I have it all completed (for seeding) but its also occurs when you do force-recheck, the problem is that ALL files that is checking goes straight to Physical Memory, If I have 4GB of rams and I try to do recheck on 10-30GB torrent its not gonna happen, but it will use ALL of mine PC RAMS. You can try to force-recheck of torrent 2-3x times bigger then you have RAMS and you will see if you still haven't understood what i said. BTW its only occurs on 1,3,2 version. I tried to explain as good as possible, hope you understand and will fix it.

Change History (12)

comment:1 Changed 6 years ago by ccmorris

This occurs because Deluge attempts to make a memory mapped file when checking. It maxes out my memory, until I pause so it stops checking. Then the memory usage returns to normal.

See this thread

comment:2 Changed 6 years ago by andar

We did switch to libtorrent 0.15 in the 1.3.2 windows package.

comment:3 Changed 6 years ago by ccmorris

It seems that is an issue in libtorrent 0.15. There is a ticket at the libtorrent site regarding this issue.

A suggested solution was to "disable os cache for aligned files". I don't know if that is the same cache in Deluge preferences or not. I set the cache size in preferences to 0 but it didn't solve the problem.

comment:4 Changed 6 years ago by andar

  • Status changed from new to pending

I've committed a change that was suggested in that libtorrent ticket. Could you please test this on Windows to see if it fixes the problem for you?

http://git.deluge-torrent.org/deluge/commit/?h=1.3-stable&id=52bf08dfd107e497e75ea6bf9993fb59c76b8cc2

comment:5 Changed 6 years ago by ccmorris

I don't know how to build it on Windows. First attempt failed. Is there step-by-step instructions somewhere?

comment:6 Changed 6 years ago by andar

Oh, you could probably just drop in the modified core.py into your installed Deluge directory.

I think the default puts Deluge in C:\Program Files\Deluge and in there somewhere is the where all the .pyc files are.. If you can find deluge/core/core.pyc just drop in the core.py from 1.3-stable and it should replace the .pyc when you start Deluge.

comment:7 Changed 6 years ago by ccmorris

I reinstalled 1.3.2 and replaced Deluge/deluge-1.3.2-py2.6.egg/deluge/core/core.pyc with the core/core.py that was in the latest commit. Then started Deluge and got a nasty message that there was something wrong with loading core.pyc. The exact error was "ImportError?: Bad magic number in c:\program files (x86)\deluge\deluge-1.3.2-py2.6.egg\deluge\core\core.pyc". Any thoughts? Thanks for helping me out with this.

comment:8 Changed 6 years ago by andar

You replaced it? You shouldn't do that.. You can delete the .pyc thats there and drop in the core.py file, but don't name the core.py as core.pyc as you need to let python compile it into the .pyc file.

comment:9 Changed 6 years ago by ccmorris

Ahh okay. I understand. I am a python noob lol. Deluge starts fine now but the memory problem persists.

comment:10 Changed 6 years ago by Cas

  • Status changed from pending to assigned
  • Summary changed from Stucks at Checking to Memory problems with Deluge and libtorrent v0.15 on Windows

comment:11 Changed 6 years ago by Cas

  • Owner set to andar

comment:12 Changed 6 years ago by Cas

  • Resolution set to fixed
  • Status changed from assigned to closed

Fixed in 1.3.3

Note: See TracTickets for help on using tickets.