deluge crash on windows

[loki]

Never noticed that problem, my computer is on 100% duty.

[BaNaNa]

When mine crashes, it hangs the whole computer too

and it seems that each time it crashes, there is no changes to the %, just the old % which i started (even when i set to compact allocation)
deluge seems to be working fine on my first try, no crashes, no bugs, no problems
it all started after a clean restart

[clumpco]

Hi,
Installed Deluge 0.5.8.9 yesterday.
Crashed during checking of 3rd torrent added (already downloaded) - (deluge_core!initdeluge_core)
Crashed later due to no specific reason - (ntdll!wcslen)
Crashed just now while moving the window - (msvcrt!memcpy)

I am not getting the C library error/warning.

This is running on WIndows server 2003 32bit, under Terminal Services client, no IPV6 installed - however I do no think that this is the culprit in this case since there is no error/warning.

Any ideas?
Thanks in advance

[sangfroid]

hi, i've recently found deluge torrents client and switched over from flashget. when the windows port kep crashing, i decided to go through the forum to see if other xp users were crashing for similar reasons. But no one has mentioned it yet, so i registered to post how mine crashes.

For my pc, the crash has something to do with the mouse or the machine being idle. I installed deluge on my work and home pc. I use the work pc the whole day so it rarely stays idle for more than 1 hour. And it never crashes while i'm using the pc. Same with home, when i get home, i use the pc from 9~12 and it doesn't crash while i use it. But when the computer goes idle for a long time, like when i leave home for work, when i come back, the home pc's deluge shows crash error. and same with work, when i leave my work pc on to finish a download.

to test this out, one day, i left rainbow six vegas 2 running in the back ground. And deluge didn't crash. So the crashing for me seems to have something to do with the mouse or something going idle. Hope this helps track down the crash bugs because deluge so far is a better organized client for me.

I actually thought that what the above poster said wouldn't work for me, but amazingly it did. Lemme explain, I've got a single system at home running Windows XP SP2. The machine is on 24/7 and deluge 0.5.9 has been active with the same problem that some of the others is having. It crashes every now and then.

The crashes do tend to happen when I'm not at my system (it's occured once or twice when I am), and especially prevalent overnight when I'm asleep and the machine isn't being accessed.

So I tried to do some tests at the beginning of this week (Sunday, May 4th), I tried running a game (Sid Meier's Pirates) and leaving it at the intro screen overnight to see what would happen. Deluge crashed.

Don't have many games installed, especially one that loops and can keep the system non-idle so to speak, the next night (Monday, May 6th) I tried running Crysis. Left it at the intro screen / main menu. It didn't crash.

Left the house in the morning, forgot that I had quit Crysis and didn't run it again before I left, and Deluge crashed by the time I got home at noon.

Tried the process again with Crysis. Everytime I left the system to idle (having dinner, taking a bath, going out for a short while) I'd make sure to run Crysis and just leave it at the main menu. Deluge hasn't crashed since then (afternoon of Monday, May 6th) until now, 4 full days which is remarkable considering the fact that I used to have crash at least once a day (typically 2-3 times).

A friend suggested maybe I should set the Deluge's program priority in Windows higher. I'll try that later on to see if it makes any difference.

Anyway, just my 2 cents contribution to the crashing thread. Gotta admit, I love the client. The speeds that I get really rock considering the amount of traffic shaping that goes on by my ISP.

Good job guys!

[woofwoof]

I've been using deluge for over 1/2 year on Windows, & the causes of my crashes are the followings
1. IPv6 used by asio library exception not handled causing the VC++ exception error
2. Older library or mismatch library when installing newer version on top of previous installation
3. For some reason deluge always crash on my AMD64 dual core machine after few minutes or hours. My solution is to set the cpu affinity to 1 of the processor for deluge. Since then no crashes as well for couple of months. It may be caused by the prebuilt library or the gcc version that I used to compile the deluge, I'm not sure. I lazy to find it out.

[noian]

Usually, deluge crashes randomly (might be because my CPU sometimes hiccups randomly (maybe once per 4 hours on?), and its not over-clocked, might need a new one soon), but the "deluge has encountered a problem" error box appears, and if I ignore the box, deluge still runs fine on the background (as in it still downloads things, things still work, etc.) but the next start up of deluge, everything that was downloaded/uploaded is lost (might be associated with the reason of why deluge sometimes doesn't write the downloaded files until close)....kinda kills the prospect of leaving the computer on and going away to get upload ratio to 1.000 or above since it can "crash" at anytime and everything sent afterward is lost.

[sangfroid]

Decided to experiment further since my last post based on the suggestion of a friend that I should try setting the Windows priority for Deluge higher.

So I set it to realtime priority. Regular routines of leaving my machine idle, but didn't bother to run Crysis anymore when so. It's been more then 24 hours without a crash, which is pretty awesome.

For those who'd like to experiment with this and see whether it does you any good:

Assuming you're running Windows XP, with Deluge running, press CTRL-ALT-DEL to bring up windows task manager.. Under the "Processes" tab, look for deluge.exe. Right click on it, select "Set Priority" -> "Realtime". Close windows task manager, and carry on and see if it helps.

Cheers.

[TaperHarley]

Hi

I just tried that real time priority thing with a clean install of 0.5.9.0 and it didn't help. I have about 50 gigs worth of torrents and it crashed during hash check, and yes the pc was unattended. The good news is that it didnt' forget the settings and how far it get with the checking. But I'm gonna put the test one step further. I'll mess with the "affinity" thing instead. Running it on one cpu and forget about priority to see what that does I have a simple P4 with hyperthreading.
P4@3000, 2gigs of RAM.

"Great Success!" Deluge ran for 10 hours unattended affinity works for me

[woofwoof]

Seems like deluge for windows had thread race issue. Setting the priority won't help at all. Setting affinity does help in my case. Anyhow just wanna list down the symptoms to help you guys identify the most common problem with deluge for windows.

1. IPv6 - You will see the unhandled VC++ Exception window, but deluge will continue downloading until you close the exception window which will then terminate deluge.

2. MP thread race issue? - Windows exception (with error icon) usually related to invalid memory access in memory operation/function, in system dlls. Deluge may continue downloading for a while, but will eventually stop downloading & responding.

VC++ Exception windows & Windows Exception window is different. Unless if it is intercepted by error reporting service.

[TaperHarley]

Hi all,

Last night I was running Deluge on cpu0 and on above normal priority. It ran for a little over 4 hours. After that I found my pc "turned off" When I tried turning it on it just wouldn't. I switched off the PSU, left it like that for minutes switched back on and thank God, my pc worked again. I run my pc 24/7 torrenting, but I gotta tell you that I won't touch Deluge again for four more versions at least