Opened 9 years ago

Closed 7 years ago

#9953 closed Bug report (outdated)


Reported by: lostinlodos Owned by:
Priority: normal Component: FileZilla Client
Keywords: crash, security, memory Cc:
Component version: Operating system type: Windows
Operating system version: 6.1:7601 Windows 7 ultimate x64


Crash on load
Problem signature:

Problem Event Name: APPCRASH
Application Name: filezilla.exe
Application Version:
Application Timestamp: 00000006
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521ea8e7
Exception Code: c0000005
Exception Offset: 0002e3be
OS Version: 6.1.7601.
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Change History (6)

comment:1 by Tim Kosse, 9 years ago

Status: newmoreinfo

Which version of FileZilla are you using?

What did you do with FileZilla when it crashed?

Can you reproduce the crash? If so, what are the steps to reproduce it?

comment:2 by Jarek, 9 years ago

Got same situation here on latest Beta 3


  • Provider [ Name] Application Error
  • EventID 1000 [ Qualifiers] 0 Level 2 Task 100 Keywords 0x80000000000000
  • TimeCreated [ SystemTime] 2014-12-27T01:46:28.000000000Z EventRecordID 55834 Channel Application Computer Ivana-Karaja Security
  • EventData

C:\Program Files (x86)\FileZilla FTP Client\filezilla.exe

FileZilla will simply not load at all, close itself without any error message after few seconds, FileZilla main window cannot be seen.

comment:3 by Tim Kosse, 9 years ago

Please try the latest nightly from

comment:4 by lostinlodos, 9 years ago

Keywords: security memory added
Status: moreinfonew beta 2 -> beta 3

Repeatable but issue found.
Looks like the installer is not clearing the populated memory on inplace upgrade.
A reboot solved the issue in the first place.
However on playing with the issue I found that purging the memory with various system tools also solved the problem. This points to some bits (no pun intended) of incompatible data being left in memory.
Setting the memory clear function in the installer should solve the issue.

This /could/ be a security issue if left untreated as a broken string of memory registers could be hijacked for data mining.

comment:5 by Tim Kosse, 9 years ago

Status: newmoreinfo

Do you mean the files on disk in the installation directory when you refer to "memory"?

comment:6 by Kurt McKee, 7 years ago

Resolution: outdated
Status: moreinfoclosed
Note: See TracTickets for help on using tickets.