Memory leak?

Specific support for Deluge on Microsoft Windows OS
darkdevil1
New User
New User
Posts: 4
Joined: Sat Mar 27, 2010 10:55 pm

Re: Memory leak?

Post by darkdevil1 »

I'm also using W7 64bit. I can't say I've noticed the memory leak, but I'll keep an eye on it.

I did however have the same problem as you where it won't start up. Issue popped up when I installed 1.2.3, but 1.2.2 was also acting up (frequent crashes).

Went ahead and completely uninstalled, as well as manually deleting the deluge folder in appdata\roaming. Did a fresh install, and it seems to be working again...

Edit: I right click one of my torrents to edit trackers, program crashes, and now I'm running into the same problem *again*. Pops up, dissapears, doesn't run.
Edit2: And now, when I try to open a freshly downloaded torrent, it works again... is there any reports I can post to hopefully help fix these crashes?
johnnyg
Top Bloke
Top Bloke
Posts: 1522
Joined: Sun Oct 28, 2007 4:00 am
Location: Sydney, Australia

Re: Memory leak?

Post by johnnyg »

darkdevil1 wrote:Edit2: And now, when I try to open a freshly downloaded torrent, it works again... is there any reports I can post to hopefully help fix these crashes?
http://dev.deluge-torrent.org/wiki/Faq# ... tshouldIdo
fukt
Member
Member
Posts: 24
Joined: Wed Feb 24, 2010 6:18 pm

Re: Memory leak?

Post by fukt »

Just wanted to say that I've got this same issue using Deluge 1.2.3 in Windows 7 x64. All 6 GB of memory gets maxed out after a couple of hours but not always. Seems to happen more when it's very active.

Do you think any clues would show up in the logs? I'll try activating logging.
dumbledore

Re: Memory leak?

Post by dumbledore »

sorry to revive an old thread, but i had a similar problem for a long time with utorrent. i eventually concluded that its not the client's fault at all, but it's actually windows buffering the data off of your hard drive and into memory. but for some reason, the windows disk cache manager gets confused and over-allocates sometimes, leading to the 100% memory usage. (i helped remedy the problem on my machine by doubling my amount of ram, since there's not much hope of getting microsoft to fix it...)
Post Reply