Opened 16 years ago
Last modified 9 years ago
#4022 closed Bug report
FileZilla crashes while processing a queue — at Initial Version
Reported by: | Jason Mount | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | FileZilla Client |
Keywords: | crash queue | Cc: | |
Component version: | Operating system type: | Windows | |
Operating system version: | 5.1.2600.5657 |
Description
FileZilla Client 3.1.5.1
Windows XP MCE 2002 + SP3
The client crashes reproducably while processing a large queue. Every time I start running my queue when I come back to the system, it has crashed.
I couldn't locate any symbols for FileZilla.
I have attached a minidump, and I have a full process dump I extracted it from if you need it.
================== !analyze -v ====================
FAULTING_IP:
filezilla+528329
00928329 8b02 mov eax,dword ptr [edx]
EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00928329 (filezilla+0x00528329)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Attempt to read from address 00000004
DEFAULT_BUCKET_ID: INVALID_POINTER_READ
PROCESS_NAME: filezilla.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
READ_ADDRESS: 00000004
FAULTING_THREAD: 00001158
PRIMARY_PROBLEM_CLASS: INVALID_POINTER_READ
BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ
LAST_CONTROL_TRANSFER: from 005540e7 to 00928329
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
0022f4f0 005540e7 0022f57c 00000004 0022f530 filezilla+0x528329
0022f510 0055dcd4 0022f57c 00000000 0022f83c filezilla+0x1540e7
0022f5d0 0055e3e6 01573b90 0022f83c 0055e1d6 filezilla+0x15dcd4
0022f770 00546b4d 01573b90 0022f83c 00000001 filezilla+0x15e3e6
0022f7a0 004c30c0 01573b90 0022f83c 00000000 filezilla+0x146b4d
0022f950 004c3dfe 0157be18 013effa0 00000001 filezilla+0xc30c0
0022f9d0 004c423f 0157be18 013effa0 040f6360 filezilla+0xc3dfe
0022fa00 004c436f 0157be18 013effa0 040f6360 filezilla+0xc423f
0022fa20 0081c0ef 0157be18 015a1230 004c4300 filezilla+0xc436f
0022fa50 0081c900 00aad320 0157be18 015a1230 filezilla+0x41c0ef
0022fa80 0081cc3b 00aad2ec 015a1230 0157be18 filezilla+0x41c900
0022faa0 0081ceff 0157be18 015a1230 015a1230 filezilla+0x41cc3b
0022fb10 00857305 0157be18 0404d498 01383420 filezilla+0x41ceff
0022fb30 00911960 013831c8 00911949 0003016f filezilla+0x457305
0022fb50 7e42b372 00000000 00000001 0022fbec filezilla+0x511960
0022fb6c 7e42b317 00030000 00000001 0022fbec user32!DispatchHookW+0x31
0022fba8 7e4278d0 0022fbdc 0022fbec 0022fc08 user32!CallHookWithSEH+0x21
0022fbcc 7c90e453 0022fbdc 00000030 00030000 user32__fnHkINLPMSG+0x25
0022fc08 7e4191be 7e4191f1 0022fc90 00000000 ntdllKiUserCallbackDispatcher+0x13
0022fc28 007cceb8 0022fc90 00000000 00000000 user32NtUserGetMessage+0xc
0022fcb8 007d1724 01592760 00400000 0022fd28 filezilla+0x3cceb8
0022fd28 00773c8a 01592760 00320035 0022fda8 filezilla+0x3d1724
0022fda8 008933b7 013831c8 003f6ad8 00aaa010 filezilla+0x373c8a
0022fe08 00771e89 0022fea8 003f6ad8 00000001 filezilla+0x4933b7
0022feb8 0042c1ab 00400000 00000000 00252356 filezilla+0x371e89
0022fed8 008e4719 00400000 00000000 00252356 filezilla+0x2c1ab
0022ff58 004010a7 004012f0 009b3b94 0022ff78 filezilla+0x4e4719
0022ffa0 00401123 00000002 aefa2d08 7c90dc9c filezilla+0x10a7
0022ffc0 7c817067 00320035 00360034 7ffd9000 filezilla+0x1123
0022fff0 00000000 00401110 00000000 00000000 kernel32BaseProcessStart+0x23
STACK_COMMAND: ~0s; .ecxr ; kb
FOLLOWUP_IP:
filezilla+528329
00928329 8b02 mov eax,dword ptr [edx]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: filezilla+528329
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: filezilla
IMAGE_NAME: filezilla.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 491ef087
FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_filezilla.exe!Unknown
BUCKET_ID: APPLICATION_FAULT_INVALID_POINTER_READ_filezilla+528329
Followup: MachineOwner
Minidump of the crash