[RC6 (Was RC4)] Crashed when refreshing web-page
Posted: December 22nd, 2009, 5:26 pm
Hi,
Refreshed the queue-page, and the application crashed, showing the standard Windows-error.
sabnzbd.log didn't fetch the error (obviously the program crashed before something could be written, or whatnot).
This is taken from Windows Event Viewer;
Refreshed the queue-page, and the application crashed, showing the standard Windows-error.
sabnzbd.log didn't fetch the error (obviously the program crashed before something could be written, or whatnot).
This is taken from Windows Event Viewer;
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 22.12.2009
Time: 23:11:01
User: N/A
Computer: SERVER
Description:
Faulting application sabnzbd.exe, version 0.0.0.0, faulting module libeay32.dll, version 0.9.8.7, fault address 0x0004bd09.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 73 61 62 ure sab
0018: 6e 7a 62 64 2e 65 78 65 nzbd.exe
0020: 20 30 2e 30 2e 30 2e 30 0.0.0.0
0028: 20 69 6e 20 6c 69 62 65 in libe
0030: 61 79 33 32 2e 64 6c 6c ay32.dll
0038: 20 30 2e 39 2e 38 2e 37 0.9.8.7
0040: 20 61 74 20 6f 66 66 73 at offs
0048: 65 74 20 30 30 30 34 62 et 0004b
0050: 64 30 39 0d 0a d09..
Event Type: Information
Event Source: DrWatson
Event Category: None
Event ID: 4097
Date: 22.12.2009
Time: 23:11:04
User: N/A
Computer: FILSERVER
Description:
The application, C:\Program Files\SABnzbd\SABnzbd.exe, generated an application error The error occurred on 12/22/2009 @ 23:11:04.171 The exception generated was c0000005 at address 00D8BD09 (libeay32!sk_free)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
** NOTE: This was loooong, I'll provide it as a .txt if needed **
Version: 0.5.0 beta 4
OS: Windows XP SP2
Install-type: Windows Installer
Skin (if applicable): Classic white-black
Firewall Software: None
Are you using IPV6? No
Is the issue reproducible? Not yet - will post here if it happens again