Page 1 of 1

Deluge is crashing on me but no idea why

Posted: Tue Jan 30, 2018 3:28 pm
by Howski
Hi all,


Been using deluge for quite some time now and I love it. However recently Its been crashing and I have no idea why. I use a box so I'm not sat at it constantly while Deluge is working so I'm not sure when/how it crashes but it seems to do it overnight when I leave it running.

Event viewer gives me the following for the error:

Faulting application name: deluge.exe, version: 1.3.15.0, time stamp: 0x530bd002
Faulting module name: libcairo-2.dll, version: 0.0.0.0, time stamp: 0x4ecb6fdf
Exception code: 0xc0000005
Fault offset: 0x000205bd
Faulting process ID: 0x23c4
Faulting application start time: 0x01d398eaa3b8b2f4
Faulting application path: C:\Program Files (x86)\Deluge\deluge.exe
Faulting module path: C:\Program Files (x86)\Deluge\libcairo-2.dll
Report ID: 09dccee5-f9d8-45f1-a5a1-2e9b3df00c3a
Faulting package full name:



I've read the FAQ and started Deluge with debugging and sadly all I got was an empty .log file once it had crashed.

My only other clue is there are lot of deluge icons in the task bar when I open it.

Sorry to be so vague but thats it in terms of symptoms.

The PC is running Windows 10 and Deluge 1.3.15

Thanks in advance!

Re: Deluge is crashing on me but no idea why

Posted: Wed Mar 21, 2018 9:10 am
by adamralph
I get this 2 or 3 times per day:
Faulting application name: deluge.exe, version: 1.3.15.0, time stamp: 0x530bd002
Faulting module name: libglib-2.0-0.dll, version: 2.28.8.0, time stamp: 0x4e253544
Exception code: 0x40000015
Fault offset: 0x0004c2d8
Faulting process ID: 0x2cb4
Faulting application start time: 0x01d3c057dd973408
Faulting application path: C:\Program Files (x86)\Deluge\deluge.exe
Faulting module path: C:\Program Files (x86)\Deluge\libglib-2.0-0.dll
Report ID: 989956ee-ba4e-4688-b181-342aa6cfa42a
Faulting package full name:
Faulting package-relative application ID:

Re: Deluge is crashing on me but no idea why

Posted: Sun Nov 20, 2022 10:39 pm
by ScubaCaribe
Did you ever find out how to resolve this issue? I'm receiving the same exception code but with a different dll. Just posted about it here:

viewtopic.php?f=12&t=56351