Custom Query (4044 matches)

I just downloaded the update to this version last night to my Desktop Computer (Windows 7 64-bit) and to my laptop (Windows XP Build 2600, Service Pack 3) computers. On BOTH computers, I am now getting a message that says "Error: Could not connect to server" message, no matter what I try to do. I called my Site Host (GoDaddy) and they tried guiding me through, noting that it connected just fine on their side. We tried shutting off my firewalls and various other efforts on their side, to see if they could help me make it work. They finally discovered that it was a problem with the FileZilla program, but that they did not have the updated version in their system to try and see if this problem could be resolved anymore from their side. They then directed for me to contact your company in order to see if this problem could be fixed. Please help me with this right away, as I need to upload dire updates to my company website and cannot do so using the new FileZilla, which was uploaded. This is an EXTREMELY URGENT situation. Thank you very much... Jim

I just run into a problem when downloading (via sftp) multiple files simultaneously. When starting to precess the queue, the filezilla client crash after a few seconds. When downloading a singe file, there is no problem. It's reproducible, I've tried this three times (rebooted the system between, etc.).

After downgrade to 3.37.4 (win64) all is fine again.

I upgraded from 3.42.0 to 3.42.1 using FileZilla_3.42.1_macosx-x86_sponsored-setup.dmg and get the error that FileZilla 3.42.1 doesn't work with MacOS 10.13.6, required 10.14 or later. I'm using 10.13.6; 3.42.0 worked fine. The downloads page says "Requires OS X 10.9 or newer", https://filezilla-project.org/download.php?type=client. The release notes for 3.42.1 says it fixed a bug about compatibility with 10.13. However, the fix apparently made it impossible to work with 10.13. Does FileZilla no longer work with Mac OS X 10.13.6, or is a bug fix in the offing?

after update to 3.5.0 (was working fine between same two machines a couple of days ago - only significant change is FileZilla client upgrade) connecting to one of my servers takes down my wireless router. By which I mean it kills the connection between client machine and router, and also connection between iMac (different machine) and iPhone.

Steps: 1) wireless connected fine on all three devices. these are the only devices connected to wireless, and client machine (Win7 laptop) and iMac are not using DHCP (iPhone is) 2)Attempt connection to a specific server (which happens to be running FileZilla Server - message logs from both ends of connection at bottom of report). Initial connection fine, but on the PORT step connection hangs. As I say, this worked fine between the same two machine in 3.4.x just a couple of days ago 3)All three devices are no longer able to connect to wireless. 4)Physically reset wireless router 5)Rinse and repeat (6 - 8 times before filing bug report)

Other notes: 1) windows command-line ftp works fine to drop files between these two machines

Client message log: 06:33:25 Trace: CControlSocket::DoClose(64) 06:33:25 Trace: CControlSocket::DoClose(64) 06:33:25 Status: Connecting to 208.116.32.234:21... 06:33:25 Status: Connection established, waiting for welcome message... 06:33:25 Trace: CFtpControlSocket::OnReceive() 06:33:25 Response: 220-Welcome to the FTP Server of Niche Music Group. 06:33:25 Trace: CFtpControlSocket::OnReceive() 06:33:25 Response: 220- 06:33:25 Response: 220-FileZilla Server version 0.9.37 beta 06:33:25 Response: 220-written by Tim Kosse (Tim.Kosse@…) 06:33:25 Response: 220 Please visit ​http://sourceforge.net/projects/filezilla/ 06:33:25 Trace: CFtpControlSocket::SendNextCommand() 06:33:25 Command: USER web_admin 06:33:25 Trace: CFtpControlSocket::OnReceive() 06:33:25 Response: 331 Password required for web_admin 06:33:25 Trace: CFtpControlSocket::SendNextCommand() 06:33:25 Command: PASS 06:33:25 Trace: CFtpControlSocket::OnReceive() 06:33:25 Response: 230 Logged on 06:33:25 Status: Connected 06:33:25 Trace: CFtpControlSocket::ResetOperation(0) 06:33:25 Trace: CControlSocket::ResetOperation(0) 06:33:25 Trace: CFileZillaEnginePrivate::ResetOperation(0) 06:33:25 Status: Retrieving directory listing... 06:33:25 Trace: CFtpControlSocket::SendNextCommand() 06:33:25 Trace: CFtpControlSocket::ChangeDirSend() 06:33:25 Command: PWD 06:33:25 Trace: CFtpControlSocket::OnReceive() 06:33:25 Response: 257 "/" is current directory. 06:33:25 Trace: CFtpControlSocket::ResetOperation(0) 06:33:25 Trace: CControlSocket::ResetOperation(0) 06:33:25 Trace: CFtpControlSocket::ParseSubcommandResult(0) 06:33:25 Trace: CFtpControlSocket::ListSubcommandResult() 06:33:25 Trace: state = 1 06:33:25 Trace: CFtpControlSocket::SendNextCommand() 06:33:25 Trace: CFtpControlSocket::TransferSend() 06:33:25 Trace: state = 1 06:33:25 Command: TYPE I 06:33:25 Trace: CFtpControlSocket::OnReceive() 06:33:25 Response: 200 Type set to I 06:33:25 Trace: CFtpControlSocket::TransferParseResponse() 06:33:25 Trace: code = 2 06:33:25 Trace: state = 1 06:33:25 Trace: CFtpControlSocket::SendNextCommand() 06:33:25 Trace: CFtpControlSocket::TransferSend() 06:33:25 Trace: state = 2 06:33:25 Command: PORT 69,128,109,218,193,134 06:33:45 Error: Connection timed out 06:33:45 Trace: CControlSocket::DoClose(2050) 06:33:45 Trace: CFtpControlSocket::ResetOperation(2114) 06:33:45 Trace: CControlSocket::ResetOperation(2114) 06:33:45 Trace: CFtpControlSocket::ResetOperation(2114) 06:33:45 Trace: CControlSocket::ResetOperation(2114) 06:33:45 Error: Failed to retrieve directory listing 06:33:45 Trace: CFileZillaEnginePrivate::ResetOperation(2114)

Server message log for same connection:

(000836)6/10/2011 4:12:25 AM - (not logged in) (69.128.109.218)> Connected, sending welcome message... (000836)6/10/2011 4:12:25 AM - (not logged in) (69.128.109.218)> 220-Welcome to the FTP Server of Niche Music Group. (000836)6/10/2011 4:12:25 AM - (not logged in) (69.128.109.218)> 220- (000836)6/10/2011 4:12:25 AM - (not logged in) (69.128.109.218)> 220-FileZilla Server version 0.9.37 beta (000836)6/10/2011 4:12:25 AM - (not logged in) (69.128.109.218)> 220-written by Tim Kosse (Tim.Kosse@…) (000836)6/10/2011 4:12:25 AM - (not logged in) (69.128.109.218)> 220 Please visit ​http://sourceforge.net/projects/filezilla/ (000836)6/10/2011 4:12:25 AM - (not logged in) (69.128.109.218)> USER web_admin (000836)6/10/2011 4:12:25 AM - (not logged in) (69.128.109.218)> 331 Password required for web_admin (000836)6/10/2011 4:12:25 AM - (not logged in) (69.128.109.218)> PASS (000836)6/10/2011 4:12:25 AM - web_admin (69.128.109.218)> 230 Logged on (000836)6/10/2011 4:12:25 AM - web_admin (69.128.109.218)> SYST (000836)6/10/2011 4:12:25 AM - web_admin (69.128.109.218)> 215 UNIX emulated by FileZilla (000836)6/10/2011 4:12:25 AM - web_admin (69.128.109.218)> FEAT (000836)6/10/2011 4:12:25 AM - web_admin (69.128.109.218)> 211-Features: (000836)6/10/2011 4:12:25 AM - web_admin (69.128.109.218)> MDTM (000836)6/10/2011 4:12:25 AM - web_admin (69.128.109.218)> REST STREAM (000836)6/10/2011 4:12:25 AM - web_admin (69.128.109.218)> SIZE (000836)6/10/2011 4:12:25 AM - web_admin (69.128.109.218)> MLST type*;size*;modify*; (000836)6/10/2011 4:12:25 AM - web_admin (69.128.109.218)> MLSD (000836)6/10/2011 4:12:25 AM - web_admin (69.128.109.218)> UTF8 (000836)6/10/2011 4:12:25 AM - web_admin (69.128.109.218)> CLNT (000836)6/10/2011 4:12:25 AM - web_admin (69.128.109.218)> MFMT (000836)6/10/2011 4:12:25 AM - web_admin (69.128.109.218)> 211 End (000836)6/10/2011 4:12:25 AM - web_admin (69.128.109.218)> PWD (000836)6/10/2011 4:12:25 AM - web_admin (69.128.109.218)> 257 "/" is current directory. (000836)6/10/2011 4:12:26 AM - web_admin (69.128.109.218)> TYPE I (000836)6/10/2011 4:12:26 AM - web_admin (69.128.109.218)> 200 Type set to I (000836)6/10/2011 4:12:45 AM - web_admin (69.128.109.218)> disconnected.

Folder on a FTP Server with äöü/ÄÖÜ (German umlaut) in Foldername aren't shown on FileZilla Client 3.5.3 for Mac. I tried the Windows FileZilla Client 3.5.3 and recognized, that there is no bug. It Is only a Bug at the Mac Version 3.5.3.

Just installed the FileZilla update, and it completely hangs every time I'm trying to connect to a server.

I saved the memory and hd dump from the Microsoft error report, but I don't know if I can send them without potentially exposing my accounts' passwords...

Below are my system details.

Thanks,

Oded.

FileZilla Client

Version: 3.5.3

Build information:

Compiled for: i586-pc-mingw32msvc Compiled on: x86_64-unknown-linux-gnu Build date: 2012-01-08 Compiled with: i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2) Compiler flags: -g -O2 -Wall -g -fexceptions

Linked against:

wxWidgets: 2.8.12 GnuTLS: 2.10.4

Operating system:

Name: Windows XP (build 2600, Service Pack 2) Version: 5.1 Platform: 32 bit system

I found build bug - in installer edition FileZilla 3.50 RC1/RC2 file filezilla.exe have size at 99 Mb, but in Zip edition еры file have size ~ 30 Kb and don't work. Please check this files and correct buil script's.

Best regards, Victor

I'm maintaining FileZilla at MacPorts and run into the following when compiling:

:info:build toolbar.mm:9:8: warning: instance method '-setToolbarStyle:' not found (return type defaults to 'id') [-Wobjc-method-access]
:info:build                 [tlw setToolbarStyle:NSWindowToolbarStyleExpanded];
:info:build                      ^~~~~~~~~~~~~~~
:info:build /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/AppKit.framework/Headers/NSWindow.h:185:12: note: receiver is instance of class declared here
:info:build @interface NSWindow : NSResponder <NSAnimatablePropertyContainer, NSMenuItemValidation, NSUserInterfaceValidations, NSUserInterfaceItemIdentification, NSAppearanceCustomization, NSAccessibilityElement, NSAc
cessibility>
:info:build            ^
:info:build toolbar.mm:9:24: error: use of undeclared identifier 'NSWindowToolbarStyleExpanded'
:info:build                 [tlw setToolbarStyle:NSWindowToolbarStyleExpanded];
:info:build                                      ^
:info:build 2 warnings generated.
:info:build mv -f settings/.deps/filezilla-optionspage.Tpo settings/.deps/filezilla-optionspage.Po
:info:build 1 warning and 1 error generated.
:info:build make[4]: *** [libfzmac_a-toolbar.o] Error 1

3.51 compiled just fine and it seem the change in toolbar.mm is causing this because you use setToolbarStyle:NSWindowToolbarStyleExpanded, which is only available from macOS 11.0 onwards, see ​https://developer.apple.com/documentation/appkit/nswindowtoolbarstyle/nswindowtoolbarstyleexpanded?language=objc

This is an very awkward problem.It's been annoying me on my notebook for 5 months now and when it started on my local server as well I can now track it down to the install of Filezilla 3.53.1.

First things first.

My laptop started to fail to boot into network. After some log search I always dig the following error message from syslog: Apr 15 16:50:31 Quietearth2 NetworkManager[1244]: /usr/sbin/NetworkManager: symbol lookup error: /lib/x86_64-linux-gnu/libcurl-gnutls.so.4: undefined symbol: gnutls_srp_allocate_client_credentials, version GNUTLS_3_4

Removing /usr/local/lib/libgnutls.so.30 makes network manager start again.

Now the same error ocurred on the reboot of my server after the recent first time installation of filezilla client. And the same workaround made Network-Manager start again.

It is the lib that came with filezilla.

My laptop is a Kubuntu 20.04.2 Thinkpad T460, my server is an Ubuntu 20.04.2 Dell Optiplex 7040

I downloaded the tarball of the client and copied the files from bin, lib und share in /usr/local respectively.

If I can provide further system info and logs, feel free to ask.

I suspect the libsqlite3.so.0 to have a similar problem but I can not provide the same clear evidence as above.

Hi.

There is a long list of compilation errors when I try to build FileZilla on Mageia Cauldron.

gcc -DHAVE_CONFIG_H   -I. -I../../config -DNO_GSSAPI -D_FILE_OFFSET_BITS=64    -O2 -g -pipe -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables -Wall -c -o libfzputtycommon_a-sshsha.o `test -f 'sshsha.c' || echo './'`sshsha.c
In file included from /usr/lib/gcc/i586-mageia-linux/12/include/immintrin.h:98,
                 from sshsha.c:345:
/usr/lib/gcc/i586-mageia-linux/12/include/avx512fp16intrin.h:38:9: error: '_Float16' is not supported on this target
   38 | typedef _Float16 __v8hf __attribute__ ((__vector_size__ (16)));
      |         ^~~~~~~~

Here is the full log file: ​https://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20220624173422.papoteur.duvel.689132/log/filezilla-3.60.1-3.mga9/build.i586.0.20220624173643.log

Please let me know if you need more information.

Thanks in advance.

Hello, I downloaded and installed the latest Windows 64-bit FileZilla v3.66.5 yesterday and have discovered the filezilla.exe executable contains no version information as existed in the previous versions Without this version information it is not possible to detect the correct version has been installed with automated deployment tools (such as SCCM or Intune) FileZilla.exe v3.66.5 properties will be attached as an image once the ticket has been created

Background: The Enhanced Mitigation Experience Toolkit (EMET) is a utility that helps prevent vulnerabilities in software from being successfully exploited. EMET achieves this goal by using security mitigation technologies. These technologies function as special protections and obstacles that an exploit author must defeat to exploit software vulnerabilities. These security mitigation technologies do not guarantee that vulnerabilities cannot be exploited. However, they work to make exploitation as difficult as possible to perform.

​http://support.microsoft.com/kb/2458544

Issue Since upgrading to 3.8.1, FileZilla is being terminated by EMET as it is triggering the "SimExecFlow" mitigation:

EMET detected SimExecFlow mitigation and will close the application: filezilla.exe

SimExecFlow check failed:
  Application 	: C:\Program Files (x86)\FileZilla FTP Client\filezilla.exe
  User Name 	: asdf
  Session ID 	: 1
  PID 		: 0x1198 (4504)
  TID 		: 0x2428 (9256)
  CodeAddress 	: 0x009D1909
  CodeStackPtr 	: 0x28FDB4
  CalledAddress 	: 0x753F4327
  API name 	: kernel32.VirtualProtect
  StackPtr 	: 0x0028FD98
  FramePtr 	: 0x28FDC0

As EMET is used in enterprise environments where it cannot be disabled by users, this issue prevents FileZilla from functioning. Downgrading to 3.8.0 fixes the issue.

Hi,

Since I update to 3.9.0.2 the folder "Documents and settings" of my local C drive is considered as a file (even if it still shown as a folder).

And so when I sort the local drive by name, "Documents and settings" is under every other folders which it shouldn't be. And if there is a file beginning by a letter before "D" then the file is shown before the folder "Documents and settings". So the folder "Documents and settings" appears in the middle of the files list !!!

I revert back to 3.9.0.1, everything is back to normal.

Bye

Mr Strange

I built FileZilla 3.9.0.2 against wxWidgets 3.0.1, but i don't see any information displayed in the Message Log Panel

Here's my build parameter:

LDFLAGS="-ldl" \ CFLAGS="$SLKCFLAGS" \ CXXFLAGS="$SLKCFLAGS" \ ./configure \

--prefix=/usr \ --libdir=/usr/lib64 \ --sysconfdir=/etc \ --localstatedir=/var \ --mandir=/usr/man \ --docdir=/usr/doc/filezilla-3.9.0.2 \ --disable-static \ --disable-manualupdatecheck \ --disable-autoupdatecheck \ --enable-locales \ --build=$ARCH-slackware-linux

Other info: Slackware 14.1 / current GCC 4.8.3 GTK+3-3.8.2 gnutls-3.2.15 sqlite-3.7.17

I tried to report a bug of FileZilla and the website says my version is older than the current download version. But it's exactly the opposite.

"You are using an outdated version of FileZilla. Please understand that we can not give any support for outdated versions.

Your version: 3.3.5.1 Current version: 3.5.0"

Dear Support Team,

I wanted to bring to your attention that the FileZilla Application is currently being flagged as malware by Windows Defender. Additionally, upon checking the file and URL with VirusTotal, both are identified as suspicious or potentially harmful.

I appreciate your prompt attention to this matter and look forward to your guidance on resolving this issue.

Best regards,

When attempting to clean out a directory from my server; FileZilla crashed with error "The instruction at "0x77bd8173" referenced memory at "0x01505000". The memory could not be "read"."

I was able to duplicate the crash by creating a directory with greater than 300 files and attempting to delete the upper level directory. The program successfully lists the directory contents and begins the deletion process but then shortly after it freezes and eventually abends with the above error. The files in the directory can be manually removed if done so a few at a time.

Running FileZilla 3.12.0.2, Client is Windows 7 x64. When we attempt to log in with a valid credentials, we always get the following log. We can connect with other FTP client software, including Core FTP and Windows command-line FTP with no problems. There is a timeout delay after the message it is trying to get a directory listing of the start directory ("/array1").

Status: Resolving address of ftp.internal.inceptra.com Status: Connecting to <server-ip-address>:21... Status: Connection established, waiting for welcome message... Status: Initializing TLS... Status: Verifying certificate... Status: TLS connection established. Status: Server does not support non-ASCII characters. Status: Connected Status: Retrieving directory listing of "/array1"... Status: Server sent passive reply with unroutable address. Using server address instead. Command: MLSD Error: Connection timed out after 20 seconds of inactivity Error: Failed to retrieve directory listing Status: Disconnected from server Status: Resolving address of <our-ftp-hostname> Status: Connecting to <server-ip-address>:21... Status: Connection established, waiting for welcome message... Status: Initializing TLS... Status: Verifying certificate... Status: TLS connection established. Status: Server does not support non-ASCII characters. Status: Connected Status: Retrieving directory listing of "/array1"... Status: Server sent passive reply with unroutable address. Using server address instead. Command: MLSD Error: Connection timed out after 20 seconds of inactivity Error: Failed to retrieve directory listing

Connecting from Filezilla client, (tested: running on Vista Business x64 or XP Professional x86) to a vsftpd server (running on Ubuntu 7.04 x86 and Ubuntu 8.04 x86 (two servers) ), using FTPES and TLS authentication. Works fine, but when the client is closed or the "disconnect" button is used, it doesn't seem to disconnect from the server properly, not closing down the SSL session:

Mon Oct 12 12:30:47 2009 [pid 17113] [ftpusername] OK LOGIN: Client "11.22.33.44" Mon Oct 12 12:31:11 2009 [pid 17114] [ftpusername] DEBUG: Client "11.22.33.44", "Connection terminated without SSL shutdown - buggy client?"

I get this on both servers, with all kinds of FZ-Windows clients. Other clients I tested seem to disconnect correctly.

I have several Windows clients running Windows XP Pro SP3 and Windows Vista SP1. I have FileZilla client 3.2.0 installed. All these machines have a dual IPv4 and IPv6 configuration as I am currently testing IPv6. My DNS server (Windows 2003 Server SP2) returns both IPv4 and IPv6 addresses for my servers when queried.

My FileZilla sever (0.9.30) is running on a Windows XP SP3 machine, also with a valid IPv6 configuration.

When I use the FileZilla client to try and connect to a server for which my DNS server can return both an IPv6 address and an IPv4 address, the FileZilla client always tries to use the IPv6 address in preference to the IPv4 address. This might not be an issue except that the FileZilla server does not seem to listen to/accept connections on its host's IPv6 address. As a result the client is not able to connect. I have tried changing the binding order on the client machines to make IPv4 come before IPv6 but it does not help.

This seems like a bug to me. Surely use of IPv6 should at a minimum only be by explicit request? Ideally one could specify which to use as a default at the client level and maybe also with a host specific override. I imagine mixed environments are becoming quite common and this could become a big problem.

Ticket #4204 is still an issue:

In preparation of the World IPv6 Day at 8 June 2011 we added AAAA Records in the DNS to the host names of our servers.

We can successful connect to all the services at the server via IPv6 - with the exception of the FileZilla Server, that does not offer IPv6 support.

This should not be an issue, because the Clients like web browsers or mail clients typically first try IPv6 and then fallback to IPv4, if no IPv6 connection can be established.

But the FileZilla Client does no fallback to the IPv4 address (what is also sent by the DNS server), FTP doesn't work any longer.

This could get an big issue and could cast a damning light on the FileZilla Client after IPv6 will be enabled by more and more ISP - not only at the World IPv6 Day!

Hello.

Apologies if this has already been reported - but I couldn't find anything when I did a search.

Anyway, after the latest Filezilla update to 3.10.0.2, a server I transfer files from has numerous files of over 2GB in size (a PVR with an inbuilt FTP client) - however - should there be a problem and the file needs to be resumed I am told in the message log that "Server does not support resume of files over > 2GB". Prior to the latest Filezilla update, there was no problem transferring files of any size - the server that the files are being transferred from has not had any software changes prior to or after the latest Filezilla update. The previous version of Filezilla that was installed was 3.10.0

• Connected to server

Reeds verbonden

FileZilla is reeds verbonden met een server.

Verbinding maken in een nieuwe tab

Change: Vorige verbinding afbreken en verbinden in nieuwe tab.

Into:

Vorige verbinding afbreken en verbinden in huidige tab.

FileZilla Client 3.1.2 segfaults shortly after it has connected to an FTP server.

I don’t think this is important, but the last lines I can read in the log window are:

TYPE I
200 Switching to Binary mode.
PASV

This part of my gdb session should be helpful for those who understand it …:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb62b9710 (LWP 7323)]
0xb79c9e51 in subcolor () at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/regex/regc_color.c:356
356             co = GETCOLOR(cm, c);
(gdb) bt
#0  0xb79c9e51 in subcolor () at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/regex/regc_color.c:356
#1  0xb79cacc8 in onechr () at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/regex/regcomp.c:1552
#2  0xb79cc06b in parsebranch () at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/regex/regcomp.c:847
#3  0xb79cbd7f in parse () at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/regex/regcomp.c:624
#4  0xb79cc745 in parsebranch () at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/regex/regcomp.c:885
#5  0xb79cbd7f in parse () at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/regex/regcomp.c:624
#6  0xb79ce657 in wx_re_comp () at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/regex/regcomp.c:372
#7  0xb796e40d in wxRegExImpl::Compile (this=0x8838840, expr=@0xbfd51d94, flags=0) at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/common/regex.cpp:296
#8  0xb796e5b9 in wxRegEx::Compile (this=0xbfd51d64, expr=@0xbfd51d94, flags=0) at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/common/regex.cpp:625
#9  0x08182474 in CFtpControlSocket::ParsePasvResponse (this=0x8875d20, pData=0x8826000) at ftpcontrolsocket.cpp:3655
#10 0x08182e6a in CFtpControlSocket::TransferParseResponse (this=0x8875d20) at ftpcontrolsocket.cpp:3906
#11 0x0818c478 in CFtpControlSocket::ParseLine (this=0x8875d20, line={<wxStringBase> = {static npos = 4294967295, m_pchData = 0xbfd51ea0}, <No data fields>})
    at ftpcontrolsocket.cpp:385
#12 0x0818d002 in CFtpControlSocket::OnReceive (this=0x8875d20) at ftpcontrolsocket.cpp:287
#13 0x08170c6b in CRealControlSocket::OnSocketEvent (this=0x8875d20, event=@0x882c610) at ControlSocket.cpp:979
#14 0xb791e9a8 in wxAppConsole::HandleEvent (this=0x8343b80, handler=0x8875d20, func=&virtual table offset 136, event=@0x882c610)
    at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/common/appbase.cpp:322
#15 0xb79bcdea in wxEvtHandler::ProcessEventIfMatches (entry=@0x824d400, handler=0x8875d20, event=@0x882c610)
    at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/common/event.cpp:1231
#16 0xb79bdfe4 in wxEventHashTable::HandleEvent (this=0x824d500, event=@0x882c610, self=0x8875d20)
    at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/common/event.cpp:906
#17 0xb79be0eb in wxEvtHandler::ProcessEvent (this=0x8875d20, event=@0x882c610) at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/common/event.cpp:1293
#18 0xb79bd269 in wxEvtHandler::ProcessPendingEvents (this=0x8875d20) at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/common/event.cpp:1191
#19 0xb791ed21 in wxAppConsole::ProcessPendingEvents (this=0x8343b80) at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/common/appbase.cpp:294
#20 0xb7c25a01 in wxAppBase::ProcessIdle (this=0x8343b80) at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/common/appcmn.cpp:435
#21 0xb7b76003 in wxapp_idle_callback () at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/gtk/app.cpp:206
#22 0xb6fc9ae1 in g_idle_dispatch () at gmain.c:4090
#23 0xb6fcbb08 in g_main_context_dispatch () at gmain.c:2012
#24 0xb6fcf333 in g_main_context_iterate () at gmain.c:2645
#25 0xb6fcf82a in g_main_loop_run () at gmain.c:2853
#26 0xb73367c9 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#27 0xb7b8fa75 in wxEventLoop::Run (this=0x8804b48) at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/gtk/evtloop.cpp:76
#28 0xb7c2586e in wxAppBase::MainLoop (this=0x8343b80) at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/common/appcmn.cpp:312
#29 0xb7c25441 in wxAppBase::OnRun (this=0x230) at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/common/appcmn.cpp:367
#30 0xb7957e9a in wxEntry (argc=@0xb7a258ac, argv=0x8343c38) at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/common/init.cpp:460
#31 0xb7958087 in wxEntry (argc=@0xbfd52330, argv=0xbfd523b4) at /usr/src/debug/x11-libs/wxGTK-2.8.8.1/wxPython-src-2.8.8.1/src/common/init.cpp:472
#32 0x080a8a3e in main (argc=1, argv=0xbfd523b4) at locale_initializer.cpp:83

installed 3.10.0 - can't log onto ftp sites. Give me access to previous build!

Error: The data connection could not be established: ECONNREFUSED - Connection refused by server Error: Connection timed out Error: Failed to retrieve directory listing

FileZilla Client

Version: 3.10.0

Build information:

Compiled for: i686-w64-mingw32 Compiled on: x86_64-unknown-linux-gnu Build date: 2015-01-07 Compiled with: i686-w64-mingw32-gcc (GCC) 4.9.1 Compiler flags: -g -O2 -Wall -g -fexceptions -std=gnu++11

Linked against:

wxWidgets: 3.0.3 GnuTLS: 3.2.20 SQLite: 3.8.7.2

Operating system:

Name: Windows 7 (build 7601, Service Pack 1), 64-bit edition Version: 6.1 Platform: 64-bit system

Hello,

Using FZ for years, to manage web sites on hosted servers. With proper settings, FZ always preserved timestamps on upload as expected.

Each time FZ proposes to update, I do it. Currently I am on version 3.16.0 (last one). Today I do major updates and detects that timestamps on hosted server are NOT preserved. I have checked that setting IS active (see capture).

Of course, I can not control whether some change on hosted server is the origin of the issue.

What can I do for further investigation? I have activated log, but no data yet, I have to do some more uploads ...

Hi Guys,

When I download the latest release of FileZilla Client for Mac, I get an error message displaying that it is not supported on this type of mac and the file might be corrupted. I'm on macOS Mojave. Any idea why? It was displaying the same error message before I upgrade to Mojave. I use FileZilla most of my time so it is kind of critical for me not to have access to it atm..

Thanks and take care! :)

I am seeing any new files added to a RHEL 5.x box using SFTP, shows file having Last Modified date that are in the future. I have seen the bug here in tickets, but it seems to just get dismissed ? If I go local to the server via ssh the dates are correct locally. I have checked the ntp server, the date/time, zones, on server and client and everything is in order. My client machine is a Windows 7 Pro sp1 64bit os.

FileZilla Client 3.9.0.2 not expanding/browsing DFS shared drives, 3.9.0.1 displays them fine, update 3.9.0.2 does not. Instead, one will see the shared drive and the root DFS namespace links but cannot browse further down then the root name spaces.

As in, the shared drive will display only 1 level down, still within DFS links, not even to the next level of DFS links, and not any further, thereby rendering them non-useable.

I've tried this on XP, Win 7, and Win 8.1. Downgrading to 3.9.0.1 resolved this issue.

I did not take a screenshot before downgrading, all you would see is that the folders have no + (PLUS symbol) next to them in the local site view, and that you can not click any further in the pane below. Right clicking and hitting "open" says "no program associated".

Same issue on multiple users machines.

Also, un-related, but SourceForge has been serving virsues up on the auto-download links and has infected machines here, I still see it offering 724K instead of the 5+MB installer for FileZilla, you may want to look into this as people are trying to download your client and ending up with malware and viruses.

Thanks!

There has been issues with connection over TLS for some ISPs

Status:	Resolving address of server.XXXXXXX.com
Status:	Connecting to XX.XX.XX.XX:21...
Status:	Connection established, waiting for welcome message...
Response:	220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
Response:	220-You are user number 1 of 50 allowed.
Response:	220-Local time is now 03:04. Server port: 21.
Response:	220-This is a private system - No anonymous login
Response:	220-IPv6 connections are also welcome on this server.
Response:	220 You will be disconnected after 15 minutes of inactivity.
Command:	AUTH TLS
Response:	502 AUTH TLS OK.
Command:	AUTH SSL
Error:	Could not connect to server
Status:	Waiting to retry...

As of now I am not having any issues while connecting with FTP inbuilt application in Windows 10

FileZilla Client fails to upload complete directories from UNC paths.

Steps to repoduce:

• Connect to remote site
• Open local UNC-based share (eg.
  somecomputer\someshare)
• Drop a folder from said local UNC-based share into

the remote site's pane

The started occuring with build 2.2.16 and exists in build 2.2.17 -- Builds prior to 2.2.16 are not affected.

This is also occurs when the local site windowpane contains an UNC path. Right-clicking a folder/directory and selecting 'Upload' does absolutely nothing.

FileZilla Client Fails to Upload Directories From UNC Paths FileZilla Client fails to upload complete directories from UNC paths.

Steps to repoduce:

• Connect to remote site
• Open local UNC-based share (eg.
  somecomputer\someshare)
• Drop a folder from said local UNC-based share into

the remote site's pane

side note:

• files work

There are old bug reports of this: 708993 1343247 1445156

If I named a folder on my ftp server like "[Movie]",then I can't use FileZilla Client to acdcess it,it will give me an error message like "550 Unable to handle command". if I change the folder name to "Movie", then everything goes on well.

FileZilla Client crashes when trying to change file access rights when entering a digital code (example: 644) (checkboxes work), but entering numbers does not. Video: ​https://youtu.be/TyrpbjZrvVk

FileZilla Client 3.53.1

FileZilla Server 0.9.41 beta running on XP_SP3 at IPv4; FileZilla Client 3.5.3/32bit on XP_SP3 atIPv6; -> ipforwarding instancy build up using linux-wrt (ipgateway.d -> login from IPv4 Client OK; all in passive mode -> after a few seconds after

EPSV -> Entering Extended Passive Mode (

|1822|)

MLSD -> 425 Can't open data connection. Error: Failed to retrieve directory listing

-> FileZilla Client crash, when running the configuration assistent

-> Passiv -> fallback to active mode -> use following IP address fed0:1874:a001::209 -> ask OS for Port -> Test -> see attached *rtf for exact crash details

When you try to right click and rename a file in the FTP window of the remote server the whole client freezes , you can't upload files , edit files or close the app without killing the app in system monitor.

Client version is 3.10.0.1

When started the debug level is 0. Go to Edit -> Settings... -> Debug section. Change 'Debug information in message log:' drop-down from '0-None' to any other, eg '1-Warning' Click OK. Changes applied then. Bot they are valid only for current instance of the client. If you exit the client and start it again the debug level will revert to 0-None

Also there isn't any key to store the value in %appdata%\FileZilla\filezilla.xml

The issue is reproduced both for fresh installation and for upgrading.

I was trying to download a folder from a Windows server today, and every time I tried, FileZilla would get in some weird loop and fail to download the files/folders.

The folder I was trying to download has 439 files, 65

folders, with a total of 178 MB of data.

I was able to reproduce this problem using both Microsoft's IIS FTP Server and FileZilla Server, so the problem is definitely with the FileZilla client.

I will attach logs from both the FileZilla client and the FileZilla server.

Dear developers,

I am currently working on an SFTP-Proxy project and I noticed a bug in your software. When closing a file handle, according to the ​SFTP specification version 12, page 35 it states the following:

The response to this request will be a SSH_FXP_STATUS message. Note that on some server platforms even a close can fail. For example, if the server operating system caches writes, and an error occurs while flushing cached writes, the close operation may fail.

In my case this is exactly what happens. When a file is not permitted through the proxy, the CLOSE will fail. The SFTP_Client from the command line in Fedora 25 respects that and will display an error if the upload is not permitted.

Screenshot from SFTP from command line:

However, FileZilla will mark the upload as a success, even though it may have failed. The only way to verify this is to look into the directory, where the failed file will not appear. However, this could be very confusing for our users and can lead to data loss.

Screenshot from FileZilla:

FileZilla Logfile:

2016-12-12 14:24:59 6847 1 Status: Connecting to 172.18.0.4:2200...
2016-12-12 14:24:59 6847 1 Status: Connection established, waiting for welcome message...
2016-12-12 14:24:59 6847 1 Response: SSH-2.0-paramiko_2.0.2
2016-12-12 14:24:59 6847 1 Error: Cannot establish FTP connection to an SFTP server. Please select proper protocol.
2016-12-12 14:24:59 6847 1 Error: Critical error: Could not connect to server
2016-12-12 14:25:07 6847 1 Status: Disconnected from server
2016-12-12 14:25:07 6847 1 Status: Connecting to 172.18.0.4:2200...
2016-12-12 14:25:07 6847 1 Response: fzSftp started, protocol_version=7
2016-12-12 14:25:07 6847 1 Command: open "root@192.168.122.97:22@172.18.0.4" 2200
2016-12-12 14:25:08 6847 1 Command: Trust new Hostkey: Once
2016-12-12 14:25:08 6847 1 Command: Pass: ***
2016-12-12 14:25:08 6847 1 Status: Connected to 172.18.0.4
2016-12-12 14:25:08 6847 1 Status: Retrieving directory listing...
2016-12-12 14:25:08 6847 1 Command: pwd
2016-12-12 14:25:08 6847 1 Response: Current directory is: "/"
2016-12-12 14:25:08 6847 1 Command: ls
2016-12-12 14:25:08 6847 1 Status: Listing directory /
2016-12-12 14:25:08 6847 1 Status: Directory listing of "/" successful
2016-12-12 14:25:10 6847 1 Status: Retrieving directory listing of "/home"...
2016-12-12 14:25:10 6847 1 Command: cd "home"
2016-12-12 14:25:10 6847 1 Response: New directory is: "/home"
2016-12-12 14:25:10 6847 1 Command: ls
2016-12-12 14:25:10 6847 1 Status: Listing directory /home
2016-12-12 14:25:10 6847 1 Status: Directory listing of "/home" successful
2016-12-12 14:25:40 6847 1 Status: Retrieving directory listing of "/home"...
2016-12-12 14:25:40 6847 1 Command: ls
2016-12-12 14:25:40 6847 1 Status: Listing directory /home
2016-12-12 14:25:40 6847 1 Status: Directory listing of "/home" successful
2016-12-12 14:25:46 6847 2 Status: Connecting to 172.18.0.4:2200...
2016-12-12 14:25:46 6847 2 Response: fzSftp started, protocol_version=7
2016-12-12 14:25:46 6847 2 Command: open "root@192.168.122.97:22@172.18.0.4" 2200
2016-12-12 14:25:46 6847 2 Command: Trust new Hostkey: Once
2016-12-12 14:25:46 6847 2 Command: Pass: ***
2016-12-12 14:25:46 6847 2 Status: Connected to 172.18.0.4
2016-12-12 14:25:46 6847 2 Status: Starting upload of /home/deigner/Desktop/test_approve.txt
2016-12-12 14:25:46 6847 2 Command: cd "/home"
2016-12-12 14:25:46 6847 2 Response: New directory is: "/home"
2016-12-12 14:25:46 6847 2 Command: put "/home/deigner/Desktop/test_approve.txt" "test_approve.txt"
2016-12-12 14:25:46 6847 2 Command: local:/home/deigner/Desktop/test_approve.txt => remote:/home/test_approve.txt
2016-12-12 14:25:47 6847 2 Status: File transfer successful, transferred 20 bytes in 1 second
2016-12-12 14:25:48 6847 2 Status: Retrieving directory listing of "/home"...
2016-12-12 14:25:48 6847 2 Command: ls
2016-12-12 14:25:48 6847 2 Status: Listing directory /home
2016-12-12 14:25:48 6847 2 Status: Directory listing of "/home" successful
2016-12-12 14:25:50 6847 2 Status: Starting upload of /home/deigner/Desktop/test_deny
2016-12-12 14:25:50 6847 2 Command: put "/home/deigner/Desktop/test_deny" "test_deny"
2016-12-12 14:25:50 6847 2 Command: local:/home/deigner/Desktop/test_deny => remote:/home/test_deny
2016-12-12 14:25:52 6847 2 Status: File transfer successful, transferred 14 bytes in 2 seconds
2016-12-12 14:25:52 6847 2 Status: Retrieving directory listing of "/home"...
2016-12-12 14:25:52 6847 2 Command: ls
2016-12-12 14:25:52 6847 2 Status: Listing directory /home
2016-12-12 14:25:52 6847 2 Status: Directory listing of "/home" successful

In FileZilla Client, there is an option:

Settings -> Connection -> Reconnection settings -> Delay between failed login attempts

When I connect to the FTP server this option is effective for the control connection. However after the connection established and file is being downloaded, this option seems to be ignored for the data connections.

If the server activated anti-hammering protection and limited the maximum number of simultaneous logins I will immediately being banned.

FileZilla version tried: ANY version, even the latest 3.2.4 (as of 27th APR 2009)

Sample log: (The example below used TLS connection, Maximum number of retries: 2, Delay between failed login attempts: 5)

16:55:33	Status:	Connecting to [server ip]:21...
16:55:33	Status:	Connection established, waiting for welcome message...
16:55:33	Response:	220 FTP server ready.
16:55:33	Command:	AUTH TLS
16:55:33	Response:	234 AUTH Command OK. Initializing SSL
16:55:33	Status:	Initializing TLS...
16:55:33	Status:	Verifying certificate...
16:55:33	Command:	USER [username]
16:55:33	Status:	TLS/SSL connection established.
16:55:33	Response:	331 User name received, need password.
16:55:33	Command:	PASS ********
16:55:33	Response:	230 Ok
16:55:33	Command:	CLNT FileZilla
16:55:33	Response:	200 Noted.
16:55:33	Command:	OPTS UTF8 ON
16:55:33	Response:	200 UTF8 ON
16:55:33	Command:	PBSZ 0
16:55:33	Response:	200 PBSZ Command OK. Protection buffer size set to 0.
16:55:33	Command:	PROT P
16:55:33	Response:	200 PROT Command OK. Using Private data connection
16:55:33	Status:	Connected
16:55:33	Status:	Retrieving directory listing...
16:55:33	Command:	PWD
16:55:33	Response:	257 "/" is working directory.
16:55:33	Status:	Directory listing successful
16:55:43	Status:	Retrieving directory listing...
16:55:43	Command:	CWD downloads
16:55:43	Response:	250 CWD Command successful.
16:55:43	Command:	PWD
16:55:43	Response:	257 "/downloads/" is working directory.
16:55:43	Command:	TYPE I
16:55:43	Response:	200 Type set to I.
16:55:43	Command:	PASV
16:55:43	Response:	227 Entering Passive Mode ([server ip],9,152).
16:55:43	Command:	MLSD
16:55:44	Response:	150 File status okay; about to open data connection.
16:55:44	Response:	226 Closing data connection.
16:55:44	Status:	Directory listing successful
16:56:00	Status:	Connecting to [server ip]:21...
16:56:00	Status:	Connection established, waiting for welcome message...
16:56:00	Response:	220 FTP server ready.
16:56:00	Command:	AUTH TLS
16:56:00	Response:	234 AUTH Command OK. Initializing SSL
16:56:00	Status:	Initializing TLS...
16:56:00	Status:	Verifying certificate...
16:56:00	Command:	USER [username]
16:56:00	Status:	TLS/SSL connection established.
16:56:00	Response:	331 User name received, need password.
16:56:00	Command:	PASS ********
16:56:00	Response:	530 Maximum number of simultaneous logins reached
16:56:00	Error:	Could not connect to server
16:56:00	Status:	Connecting to [server ip]:21...
16:56:00	Status:	Connection established, waiting for welcome message...
16:56:00	Response:	220 FTP server ready.
16:56:00	Command:	AUTH TLS
16:56:00	Response:	234 AUTH Command OK. Initializing SSL
16:56:00	Status:	Initializing TLS...
16:56:01	Status:	Verifying certificate...
16:56:01	Command:	USER [username]
16:56:01	Status:	TLS/SSL connection established.
16:56:01	Response:	331 User name received, need password.
16:56:01	Command:	PASS ********
16:56:01	Response:	530 Maximum number of simultaneous logins reached
16:56:01	Error:	Could not connect to server
16:56:01	Status:	Connecting to [server ip]:21...
16:56:01	Status:	Connection established, waiting for welcome message...
16:56:01	Response:	220 FTP server ready.
16:56:01	Command:	AUTH TLS
16:56:01	Response:	234 AUTH Command OK. Initializing SSL
16:56:01	Status:	Initializing TLS...
16:56:01	Status:	Verifying certificate...
16:56:01	Command:	USER [username]
16:56:01	Status:	TLS/SSL connection established.
16:56:01	Response:	331 User name received, need password.
16:56:01	Command:	PASS ********
16:56:01	Response:	530 Maximum number of simultaneous logins reached
16:56:01	Error:	Could not connect to server

I test file download and file upload. There is a modification like follow. I found that modification occurs in download time.

ftp server : vsftpd-1.2.1-3E.1, CentOS 3.6

Kernel version : Linux version 2.4.21-

37.ELsmp ftp client : WinXP, FileZilla 2.2.27

There is no modification when I use WinXP ftp(console client) and Alftp.

The follow is result of my test.

[root@]#xxd ../ce.org > ../ce.xxd [root@]#xxd ce.org > ce.xxd [root@]# diff ce.xxd ../ce.xxd

(downloaded file) (orgfile)

86009c86009 < 014ff80: 5cba 3a54 f9c1 6aa1 a472 c9b8 72d9 2994 \.:T..j..r..r.). ---

014ff80: 5cba 3a54 e512 afe1 a472 c9b8 72d9 2994

\.:T.....r..r.). 975097c975097 < 0ee0f80: 5eec b17c ce96 6fad 8cde a2b6 6e5e 47d3 ^..|..o.....nG. ---

0ee0f80: 5eec b17c 9e13 6361 8cde a2b6 6e5e 47d3

^..|..ca....nG. 2262265c2262265 < 2284f80: 0b66 332e b941 651e 1d1d 83d8 82bc e8e7 .f3..Ae......... ---

2284f80: 0b66 332e 778d 846c 1d1d 83d8 82bc

e8e7 .f3.w..l........ 2283001c2283001 < 22d5f80: fce5 fcc1 af3b e453 4ccd de4b 9626 565d .....;.SL..K.&V] ---

22d5f80: fce5 fcc1 bdfc 12ae 4ccd de4b 9626

565d ........L..K.&V] 2625529c2625529 < 280ff80: ac6b 3913 a7b8 b17a 0ea3 e57c dd07 8ad1 .k9....z...|.... ---

280ff80: ac6b 3913 2976 f331 0ea3 e57c dd07

8ad1 .k9.)v.1...|.... 3548561c3548561 < 3625900: 1ee9 4c59 c3eb c905 2dd5 2245 0ddf 4747 ..LY....-."E..GG ---

3625900: 1ee9 4c59 6c72 5701 2dd5 2245 0ddf

4747 ..LYlrW.-."E..GG 3560185c3560185 < 3652f80: 0958 16f6 41a7 a007 e493 d169 8550 1f7d .X..A......i.P.} ---

3652f80: 0958 16f6 4a46 6d90 e493 d169 8550

1f7d .X..JFm....i.P.}

Hi, I run Windows XP SP2, and I had no problems till I upgraded to ver. 3.7.4.1. Now File Zilla crashes within seconds of it being started. Not only it crashes, but the computer shuts down and it restarts on its own. Please help. Thanks.

I am Using Windows XP SP3 & my FileZilla Client Version is 3.8.0.

Today I opened my Filezilla to access my FTP Site & received an update for version 3.8.1, and I clicked 'Install New Version'

The FileZilla got closed abruplty, i lost my FTP Connection and instead it showed a dialog-box saying 'Unsupported operating system Filezilla requires atleast Windows Vista and may not work correctly on your system. Do you really want to continue with the installation?' I pressed 'No', and found that FileZilla was still Closed.

I understand that my OS(Windows XP) is not supported by the update, but Filezilla should not close abruptly, irrespective of whether I chose to Update it or not Update it.

• Harshit

FileZilla will crash when a user creates a new file filter, is editing the rules, then switches (clicks) on another filter in the list box.

FileZilla crashes due startup and uploads.

Hello, I am trying to connect to ftpes account. I was previously connecting to it. But I have updated to the latest version recently and the application is crashing when ever I try to connect. It comes to the step Initialising TLS and crashes. Below is the error report:

Process: filezilla [2033] Path: /Applications/FileZilla.app/Contents/MacOS/filezilla Identifier: de.filezilla Version: 3.7.0.2 (3.7.0.2) Code Type: X86 (Native) Parent Process: launchd [235] User ID: 501

Date/Time: 2013-05-30 00:07:32.462 +0530 OS Version: Mac OS X 10.8.3 (12D78) Report Version: 10

Interval Since Last Report: 16520 sec Crashes Since Last Report: 4 Per-App Interval Since Last Report: 824 sec Per-App Crashes Since Last Report: 4 Anonymous UUID: F464DBA8-4864-4DDE-1A37-B312481947A9

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000fffffff4

VM Regions Near 0xfffffff4: --> shared memory 00000000ffff2000-00000000ffff3000 [ 4K] r-x/r-x SM=SHM

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 de.filezilla 0x004715f3 wxStringBase::operator=(wxStringBase const&) + 35 1 de.filezilla 0x001a984f CCertificate::CCertificate(CCertificate const&) + 175 2 de.filezilla 0x0011c802 CState::SetSecurityInfo(CCertificateNotification const&) + 386 3 de.filezilla 0x00077832 CMainFrame::OnEngineEvent(wxEvent&) + 1154 4 de.filezilla 0x0048d363 wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) + 131 5 de.filezilla 0x0048dad1 wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) + 113 6 de.filezilla 0x0048de9f wxEvtHandler::ProcessEvent(wxEvent&) + 207 7 de.filezilla 0x0048dd0b wxEvtHandler::ProcessPendingEvents() + 123 8 de.filezilla 0x004223d9 wxAppConsole::ProcessPendingEvents() + 105 9 de.filezilla 0x00487152 wxMacProcessNotifierAndPendingEvents + 34 10 de.filezilla 0x00334042 wxApp::MacHandleOneEvent(void*) + 50 11 de.filezilla 0x0033486b wxApp::MacDoOneEvent() + 123 12 de.filezilla 0x0034c563 wxEventLoop::Dispatch() + 35 13 de.filezilla 0x003bdbb8 wxEventLoopManual::Run() + 136 14 de.filezilla 0x003aa463 wxAppBase::MainLoop() + 83 15 de.filezilla 0x00453290 wxEntry(int&, wchar_t) + 160 16 de.filezilla 0x00036e28 main + 24 17 de.filezilla 0x00002476 start + 54

Thread 1:: Dispatch queue: com.apple.libdispatch-manager 0 libsystem_kernel.dylib 0x9a0719ae kevent + 10 1 libdispatch.dylib 0x97a9dc71 _dispatch_mgr_invoke + 993 2 libdispatch.dylib 0x97a9d7a9 _dispatch_mgr_thread + 53

Thread 2: 0 libsystem_kernel.dylib 0x9a0710ee workq_kernreturn + 10 1 libsystem_c.dylib 0x909920ac _pthread_workq_return + 45 2 libsystem_c.dylib 0x90991e79 _pthread_wqthread + 448 3 libsystem_c.dylib 0x90979d2a start_wqthread + 30

Thread 3: 0 libsystem_kernel.dylib 0x9a0710ee workq_kernreturn + 10 1 libsystem_c.dylib 0x909920ac _pthread_workq_return + 45 2 libsystem_c.dylib 0x90991e79 _pthread_wqthread + 448 3 libsystem_c.dylib 0x90979d2a start_wqthread + 30

Thread 4: 0 libsystem_kernel.dylib 0x9a0710ee workq_kernreturn + 10 1 libsystem_c.dylib 0x909920ac _pthread_workq_return + 45 2 libsystem_c.dylib 0x90991e79 _pthread_wqthread + 448 3 libsystem_c.dylib 0x90979d2a start_wqthread + 30

Thread 5: 0 libsystem_kernel.dylib 0x9a06e826 semaphore_timedwait_trap + 10 1 com.apple.CoreServices.CarbonCore 0x93225810 MPWaitOnSemaphore + 106 2 de.filezilla 0x0048563b wxSemaphoreInternal::WaitTimeout(unsigned long) + 27 3 de.filezilla 0x004856f4 wxSemaphore::Wait() + 36 4 de.filezilla 0x00485a1d wxConditionInternal::Wait() + 45 5 de.filezilla 0x001ce707 CSocketThread::Entry() + 263 6 de.filezilla 0x001d6026 wxThreadExImpl::Entry() + 22 7 de.filezilla 0x00486c60 wxThreadInternal::MacThreadStart(void*) + 96 8 com.apple.CoreServices.CarbonCore 0x93225a7b PrivateMPEntryPoint + 68 9 libsystem_c.dylib 0x9098f5b7 _pthread_start + 344 10 libsystem_c.dylib 0x90979d4e thread_start + 34

Thread 0 crashed with X86 Thread State (32-bit):

eax: 0x02e1b2e4 ebx: 0x004715e4 ecx: 0x00000000 edx: 0x005c2f34 edi: 0x02e1b2e4 esi: 0x02e16dd4 ebp: 0xbffff918 esp: 0xbffff8f0

ss: 0x00000023 efl: 0x00210202 eip: 0x004715f3 cs: 0x0000001b ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f

cr2: 0xfffffff4

Logical CPU: 1

Binary Images:

0x1000 - 0x6b2ff3 +de.filezilla (3.7.0.2 - 3.7.0.2) <D3A154DC-66CF-E9C0-77A1-8C24A5498EF8> /Applications/FileZilla.app/Contents/MacOS/filezilla

0x89a000 - 0x9b9ffb com.apple.WebKit (8536 - 8536.28.10) <C181C3FB-91E3-38AB-A709-6B61935B3AD8> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit 0xa6a000 - 0x16fdffb com.apple.WebCore (8536 - 8536.28.10) <AA738A8C-808D-302A-B58D-404C58075C45> /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore

0x2a00000 - 0x2abeff3 ColorSyncDeprecated.dylib (400) <35E3054C-5DF1-30D4-A368-C4FDB0992373> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/Resources/ColorSyncDeprecated.dylib 0x2b02000 - 0x2b03ffd com.apple.textencoding.unicode (2.5 - 2.5) <4E2ABBEB-1F0D-3C06-BA0C-C3CEDDF17BD2> /System/Library/TextEncodings/Unicode Encodings.bundle/Contents/MacOS/Unicode Encodings 0x2f78000 - 0x2f85ff3 com.apple.Librarian (1.1 - 1) <68F8F983-5F16-3BA5-BDA7-1A5451CC02BB> /System/Library/PrivateFrameworks/Librarian.framework/Versions/A/Librarian 0x3cce000 - 0x3cdfff7 com.apple.FCP Uncompressed 422.component (2.0.1 - 5757.41) <B7A08A5D-EEF4-3FCE-B9E4-B3828C5A32FC> /Library/QuickTime/FCP Uncompressed 422.component/Contents/MacOS/FCP Uncompressed 422 0x3ce4000 - 0x3cebffc com.apple.AppleGVAHW.component (1.1 - 1) <5DB91F15-3FD3-308F-8FC5-662562F3EA78> /System/Library/QuickTime/AppleGVAHW.component/Contents/MacOS/AppleGVAHW 0x3fe8000 - 0x3fecfff com.apple.CommonCocoaPanels (4.0 - 16) <7676B15F-69E2-39D2-9F35-9D2959A99079> /System/Library/CoreServices/CommonCocoaPanels.bundle/Contents/MacOS/CommonCocoaPanels 0x96ce000 - 0x96e5ff3 +net.telestream.license (1.1.0.1 -GC - 1.1.0.1 -GC) <4E228E42-930D-3FDF-B1EC-A871594A9BD8> /Library/Frameworks/TSLicense.framework/Versions/A/TSLicense 0xa70a000 - 0xa744fff com.apple.QuickTimeFireWireDV.component (7.7.1 - 2599.24) <1E9A8E7C-A9FD-34FD-AB7C-C3784BAB821F> /System/Library/QuickTime/QuickTimeFireWireDV.component/Contents/MacOS/QuickTimeFireWireDV 0xa750000 - 0xa861fef +net.telestream.wmv.import (3.2.0.16 - 3.2.0.16) <103E5A8B-B974-3501-B592-354F3BE438EA> /Library/QuickTime/Flip4Mac WMV Import.component/Contents/MacOS/Flip4Mac WMV Import 0xa891000 - 0xaa57ffb +net.telestream.wmv.advanced (3.2.0.16 - 3.2.0.16) <4F35D162-7339-31C9-A954-038B56FDEC40> /Library/QuickTime/Flip4Mac WMV Advanced.component/Contents/MacOS/Flip4Mac WMV Advanced 0xaaa2000 - 0xaad5ff7 com.apple.AppleAVCIntraCodec (2.1 - 6010.16) <DE2D1FF9-DAD0-32A1-A3A1-236E7007FDA1> /Library/QuickTime/AppleAVCIntraCodec.component/Contents/MacOS/AppleAVCIntraCodec 0xaae1000 - 0xab68ff7 com.apple.AppleProResCodec (3.0.3 - 5758.41) <14F2114C-6713-333D-B8A3-8C7FB5E5E066> /Library/QuickTime/AppleProResCodec.component/Contents/MacOS/AppleProResCodec 0xaba7000 - 0xabf0fff com.apple.AppleVAH264HW.component (3.0 - 3.0) <FDF1C720-ED0E-323E-BA44-21423DE18D61> /System/Library/QuickTime/AppleVAH264HW.component/Contents/MacOS/AppleVAH264HW 0xacb4000 - 0xadfffff com.apple.AppleGVAFramework (5.0.6 - 5.0.6) <103CBDDD-E0C2-3B62-923B-AA46F2AB3CD7> /System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/AppleGVA 0xae1b000 - 0xae58ff3 com.apple.DVCPROHDCodec (2.0.1 - 5708) <A7A316BF-4EC5-366E-AAAE-A3D337FE50C8> /Library/QuickTime/DVCPROHDCodec.component/Contents/MacOS/DVCPROHDCodec 0xae68000 - 0xaf05fff com.apple.AppleHDVCodec (2.0.3 - 5905.97) <24C4772E-1256-39E3-9E56-0223C2FFE080> /Library/QuickTime/AppleHDVCodec.component/Contents/MacOS/AppleHDVCodec 0xaf21000 - 0xaf42fe7 com.apple.AppleIntermediateCodec (2.0.1 - 5718) <A16F6FC6-BC4B-3E05-8340-840D64CE277C> /Library/QuickTime/AppleIntermediateCodec.component/Contents/MacOS/AppleIntermediateCodec 0xaf51000 - 0xaf67ffb com.apple.IMXCodec (2.0.1 - 5708) <BCCDCFDE-527B-3634-ABB9-E8588C91E407> /Library/QuickTime/IMXCodec.component/Contents/MacOS/IMXCodec 0xaf79000 - 0xaf91ff2 com.apple.applepixletvideo (1.2.31 - 1.2d31) <B5622D90-ADF3-3DB2-B64B-5F4AF7C274E3> /System/Library/QuickTime/ApplePixletVideo.component/Contents/MacOS/ApplePixletVideo 0xaf96000 - 0xafa4fff com.apple.iokit.IOHIDLib (1.8.1 - 1.8.1) <21036C5A-1951-38F3-9C86-0CED7F3094B0> /System/Library/Extensions/IOHIDFamily.kext/Contents/PlugIns/IOHIDLib.plugin/Contents/MacOS/IOHIDLib

0x8fecc000 - 0x8fefee57 dyld (210.2.3) <23DBDBB1-1D21-342C-AC2A-0E55F27E6A1F> /usr/lib/dyld 0x90033000 - 0x90041ff7 libz.1.dylib (43) <245F1B61-2276-3BBB-9891-99934116D833> /usr/lib/libz.1.dylib 0x90042000 - 0x902beff7 com.apple.QuickTime (7.7.1 - 2599.24) <5B1CA228-A6B3-39DF-A5CC-F981E59DAD1D> /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime 0x902c4000 - 0x902c8fff com.apple.IOSurface (86.0.4 - 86.0.4) <6431ACB6-561B-314F-9A2A-FAC1578FCC86> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface 0x902c9000 - 0x90522ff8 com.apple.JavaScriptCore (8536 - 8536.28.10) <B02A662A-7DE6-3C9D-AB08-AA746D48FF2B> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore 0x90523000 - 0x90548ffb com.apple.framework.familycontrols (4.1 - 410) <B1755756-BEA2-3205-ADAA-68FCC32E60BD> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyControls 0x90549000 - 0x9054bfff libdyld.dylib (210.2.3) <05D6FF2A-F09B-309D-95F7-7AF10259C707> /usr/lib/system/libdyld.dylib 0x9054c000 - 0x9054cfff libkeymgr.dylib (25) <D5E93F7F-9315-3AD6-92C7-941F7B54C490> /usr/lib/system/libkeymgr.dylib 0x9054d000 - 0x9065aff3 com.apple.ImageIO.framework (3.2.0 - 849) <B34C2380-51F6-38B1-BB6C-C2E5185D90EF> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO 0x90698000 - 0x906a8ff2 com.apple.LangAnalysis (1.7.0 - 1.7.0) <875363E7-6D02-3229-A9DD-E5A5568A7D61> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis 0x906a9000 - 0x90801ffb com.apple.audio.toolbox.AudioToolbox (1.8 - 1.8) <0D36953C-9897-3E9B-8C70-847E90B203A2> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox 0x90802000 - 0x90824fff libc++abi.dylib (26) <3AAA8D55-F5F6-362B-BA3C-CCAF0D3C8E27> /usr/lib/libc++abi.dylib 0x90825000 - 0x9082ffff libsystem_notify.dylib (98.5) <7EEE9475-18F8-3099-B0ED-23A3E528ABE0> /usr/lib/system/libsystem_notify.dylib 0x90830000 - 0x90847ff4 com.apple.CoreMediaAuthoring (2.1 - 914) <8D71DE7D-7F53-3052-9FAF-132CB61BA9F5> /System/Library/PrivateFrameworks/CoreMediaAuthoring.framework/Versions/A/CoreMediaAuthoring 0x90856000 - 0x90873fff libCRFSuite.dylib (33) <C9D72D0C-871A-39A2-8AFB-682D11AE7D0D> /usr/lib/libCRFSuite.dylib 0x90874000 - 0x9087fffb com.apple.DirectoryService.Framework (10.8 - 151.10) <234F4A14-60ED-300B-93B2-D5052878558F> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService 0x90880000 - 0x90896fff com.apple.CFOpenDirectory (10.8 - 151.10) <3640B988-F915-3E0D-897C-CB04C95BA601> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory 0x90897000 - 0x90911ff3 com.apple.securityfoundation (6.0 - 55115.4) <8A3DA1FE-1985-3ECB-945A-6B1E853B4BDC> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation 0x9096a000 - 0x90978fff com.apple.opengl (1.8.7 - 1.8.7) <0631EC1D-833B-39D2-A907-A9F7617E5504> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL 0x90979000 - 0x90a36feb libsystem_c.dylib (825.26) <6E35A83F-1A5B-3AF9-8C6D-D7B57B25FB63> /usr/lib/system/libsystem_c.dylib 0x912b5000 - 0x912bbfff com.apple.phonenumbers (1.1 - 47) <DD22B3D1-DA4B-3794-9D73-E90D49A1F88E> /System/Library/PrivateFrameworks/PhoneNumbers.framework/Versions/A/PhoneNumbers 0x912bc000 - 0x913f7ff7 libBLAS.dylib (1073.4) <FF74A147-05E1-37C4-BC10-7DEB57FE5326> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib 0x913f8000 - 0x913fbffc libpam.2.dylib (20) <FCF74195-A99E-3B07-8E49-688D4A6F1E18> /usr/lib/libpam.2.dylib 0x913fc000 - 0x9144cff7 com.apple.CoreMediaIO (307.0 - 4155) <49D36F54-D414-3745-8194-69FC3B632ED3> /System/Library/Frameworks/CoreMediaIO.framework/Versions/A/CoreMediaIO 0x9144d000 - 0x9144effd libunc.dylib (25) <58599CBF-E262-3CEA-AFE1-35560E0177DC> /usr/lib/system/libunc.dylib 0x9144f000 - 0x914e7fff com.apple.CoreServices.OSServices (557.6 - 557.6) <E1600639-3EEC-3DF8-BD40-747BB2117988> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices 0x914e8000 - 0x917a8ff3 com.apple.security (7.0 - 55179.11) <165A3105-9ADF-329B-93FC-3C8EFAEDDD13> /System/Library/Frameworks/Security.framework/Versions/A/Security 0x917ac000 - 0x917b6fff com.apple.DisplayServicesFW (2.7.2 - 357) <76D33A58-C39E-398A-9597-389A9B1FE76D> /System/Library/PrivateFrameworks/DisplayServices.framework/Versions/A/DisplayServices 0x917b7000 - 0x917b7fff com.apple.CoreServices (57 - 57) <956C6C6D-A5DD-314F-9C57-4A61D41F30CE> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices 0x91a2a000 - 0x91a81ff3 com.apple.HIServices (1.20 - 417) <561A770B-8523-3D09-A763-11F872779A4C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices 0x91a82000 - 0x91ad0ff3 com.apple.SystemConfiguration (1.12.2 - 1.12.2) <6E858B9F-337A-314E-88B7-24A274ACE568> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration 0x91ad1000 - 0x91bde057 libobjc.A.dylib (532.2) <FA455371-7395-3D58-A89B-D1520612D1BC> /usr/lib/libobjc.A.dylib 0x91bdf000 - 0x91c08ff7 libRIP.A.dylib (331.0.4) <FE496AFC-420A-3712-BC79-FC8C63ADB73D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib 0x91c09000 - 0x91c38ff7 com.apple.securityinterface (6.0 - 55024.4) <7C5E28DC-F8BE-3238-883F-E1646A2AF895> /System/Library/Frameworks/SecurityInterface.framework/Versions/A/SecurityInterface 0x91c39000 - 0x92056fff FaceCoreLight (2.4.1) <571DE3F8-CA8A-3E71-9AF4-F06FFE721CE6> /System/Library/PrivateFrameworks/FaceCoreLight.framework/Versions/A/FaceCoreLight 0x92057000 - 0x92d8ffff com.apple.QuickTimeComponents.component (7.7.1 - 2599.24) <51BE2DF8-7B3B-36F5-8860-50071A8702E4> /System/Library/QuickTime/QuickTimeComponents.component/Contents/MacOS/QuickTimeComponents 0x92d90000 - 0x92df6ffc com.apple.ISSupport (1.9.8 - 56) <D2AC4E10-0B3C-3194-AEB7-1E9964CBC0D0> /System/Library/PrivateFrameworks/ISSupport.framework/Versions/A/ISSupport 0x92df7000 - 0x92e07ff7 libsasl2.2.dylib (166) <D9080BA2-A365-351E-9FF2-7E0D4E8B1339> /usr/lib/libsasl2.2.dylib 0x92e08000 - 0x92eb7ff7 com.apple.CoreText (260.0 - 275.16) <873ADCD9-D361-3753-A220-CDD289196AD8> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText 0x92eb8000 - 0x92ebbffc libCoreVMClient.dylib (32.3) <35B63A60-DF0A-3FB3-ABB8-164B246A43CC> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib 0x92ebc000 - 0x92f03ff3 com.apple.CoreMedia (1.0 - 926.87) <713B7213-D695-3162-9852-DBC114C26178> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia 0x92f04000 - 0x92f43ff7 com.apple.bom (12.0 - 192) <0637E52C-D151-37B3-904F-8656B2FD44DD> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom 0x92f44000 - 0x92f48fff com.apple.CommonPanels (1.2.5 - 94) <6B3E7E53-7708-3DA2-8C50-59C2B4735DE1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels 0x92f49000 - 0x93160fff com.apple.CoreData (106.1 - 407.7) <17FD06D6-AD7C-345A-8FA4-1F0FBFF4DAE1> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData 0x93161000 - 0x93164ff7 com.apple.TCC (1.0 - 1) <437D76CD-6437-3B55-BE2C-A53508858256> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC 0x93165000 - 0x93168ff7 libcompiler_rt.dylib (30) <CE5DBDB4-0124-3E2B-9105-989DF98DD108> /usr/lib/system/libcompiler_rt.dylib 0x9318f000 - 0x93494ff7 com.apple.CoreServices.CarbonCore (1037.5 - 1037.5) <356AE2DF-ABB0-319C-8B5B-2F33D693889F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore 0x93495000 - 0x93495ffd com.apple.audio.units.AudioUnit (1.8 - 1.8) <D35BA73D-1E56-3A1D-9F9F-971F3BF8C136> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit 0x93496000 - 0x934a4fff libxar.1.dylib (105) <343E4A3B-1D04-34A3-94C2-8C7C9A8F736B> /usr/lib/libxar.1.dylib 0x934a5000 - 0x934a6fff libDiagnosticMessagesClient.dylib (8) <39B3D25A-148A-3936-B800-0D393A00E64F> /usr/lib/libDiagnosticMessagesClient.dylib 0x934a7000 - 0x934a7ffe com.apple.AOSMigrate (1.0 - 1) <4EA0829E-6AE5-3877-A5B6-032AFDF28D39> /System/Library/PrivateFrameworks/AOSMigrate.framework/Versions/A/AOSMigrate 0x934a8000 - 0x934cdff7 com.apple.quartzfilters (1.8.0 - 1.7.0) <F6A88D89-AB4A-3217-9D65-C2C259B5F09B> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzFilters.framework/Versions/A/QuartzFilters 0x934e3000 - 0x934e4fff libsystem_sandbox.dylib (220.2) <61A79095-1978-3AAA-B0E0-658BC8E5F045> /usr/lib/system/libsystem_sandbox.dylib 0x934e5000 - 0x93540fff com.apple.htmlrendering (77 - 1.1.4) <5C0C669F-AE07-3983-B38F-EB829B5CE609> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering.framework/Versions/A/HTMLRendering 0x93541000 - 0x93548ffe com.apple.agl (3.2.1 - AGL-3.2.1) <D0A9B878-7F1F-3210-B6AF-91D2DBEFF21B> /System/Library/Frameworks/AGL.framework/Versions/A/AGL 0x93553000 - 0x93553fff libsystem_blocks.dylib (59) <3A743C5D-CFA5-37D8-80A8-B6795A9DB04F> /usr/lib/system/libsystem_blocks.dylib 0x93554000 - 0x9355ffff libcommonCrypto.dylib (60027) <8EE30FA5-AA8D-3FA6-AB0F-05DA8B0425D9> /usr/lib/system/libcommonCrypto.dylib 0x93560000 - 0x93567ff3 com.apple.NetFS (5.0 - 4.0) <1F7041F2-4E97-368C-8F5D-24153D81BBDB> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS 0x93568000 - 0x935b4fff libcorecrypto.dylib (106.2) <20EBADBA-D6D6-36F0-AE80-168E9AF13DB6> /usr/lib/system/libcorecrypto.dylib 0x935b5000 - 0x935cafff com.apple.ImageCapture (8.0 - 8.0) <B8BD421F-D5A9-3FB4-8E89-AD5CFC0D4030> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture 0x935cb000 - 0x93622ff7 com.apple.ScalableUserInterface (1.0 - 1) <2B5E454B-BC49-3E85-B54D-1950397C448C> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/ScalableUserInterface.framework/Versions/A/ScalableUserInterface 0x93666000 - 0x9375eff9 libsqlite3.dylib (138.1) <AD7C5914-35F0-37A3-9238-A29D2E26C755> /usr/lib/libsqlite3.dylib 0x937a0000 - 0x93804fff com.apple.datadetectorscore (4.1 - 269.2) <B4D53047-C613-32F8-9E08-0154EA81B487> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore 0x93805000 - 0x93807ffc com.apple.QuickTimeH264.component (7.7.1 - 2599.24) <54598D54-DBFC-3EA1-9712-05F4052A79E2> /System/Library/QuickTime/QuickTimeH264.component/Contents/MacOS/QuickTimeH264 0x93808000 - 0x93808fff com.apple.quartzframework (1.5 - 1.5) <9018BE5B-4070-320E-8091-6584CC17F798> /System/Library/Frameworks/Quartz.framework/Versions/A/Quartz 0x93809000 - 0x93885ff3 com.apple.Metadata (10.7.0 - 707.5) <F2BC2AB4-A87A-3D37-A496-AC21EF3E1244> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata 0x93886000 - 0x93890fff libCSync.A.dylib (331.0.4) <71A7B331-C8A2-322C-AFB0-062EE9C3B848> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib 0x93891000 - 0x938a0fff libGL.dylib (8.7.25) <818E3E6B-9B00-3117-8157-9E95CB59A47B> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib 0x938a1000 - 0x939bdffb com.apple.desktopservices (1.7.3 - 1.7.3) <7157C51D-C695-3C9E-B532-F551E7E55B56> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv 0x939be000 - 0x939c2fff com.apple.OpenDirectory (10.8 - 151.10) <A1858D81-086F-3BF5-87E3-9B70409FFDF6> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory 0x939c3000 - 0x93a2bfe7 libvDSP.dylib (380.6) <55780308-4DCA-3B10-9703-EAFC3E13A3FA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib 0x93a2c000 - 0x93a2effb libRadiance.dylib (849) <EAF7C74F-2A71-3A07-82E1-4FADEAFCF201> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib 0x93a2f000 - 0x93a4dff3 com.apple.openscripting (1.3.6 - 148.3) <F3422C02-5ACB-343A-987B-A2D58EA2F5A8> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting 0x93a4e000 - 0x93ab2ff3 libstdc++.6.dylib (56) <F8FA490A-8F3C-3645-ABF5-78926CE9C62C> /usr/lib/libstdc++.6.dylib 0x93ab3000 - 0x9466fff7 com.apple.AppKit (6.8 - 1187.37) <6FBB3467-04F9-395F-8EA8-C84347C5BE43> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit 0x94670000 - 0x94673fff com.apple.help (1.3.2 - 42) <AD7EB1F0-A068-3A2C-9D59-38E59CEC0D96> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help 0x94674000 - 0x946b6ff7 libauto.dylib (185.1) <B2B5B639-6778-352A-828D-FD8B64A3E8B3> /usr/lib/libauto.dylib 0x946b7000 - 0x946d7ffd com.apple.ChunkingLibrary (2.0 - 133.3) <FA45EAE8-BB10-3AEE-9FDC-C0C3A533FF48> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary 0x946d8000 - 0x946e4ff8 libbz2.1.0.dylib (29) <7031A4C0-784A-3EAA-93DF-EA1F26CC9264> /usr/lib/libbz2.1.0.dylib 0x946e5000 - 0x9476dfff com.apple.PDFKit (2.7.3 - 2.7.3) <3E1B3BB0-4137-3C99-9C7D-4B34C8943F22> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framework/Versions/A/PDFKit 0x9476e000 - 0x9478dff3 com.apple.Ubiquity (1.2 - 243.15) <E10A2937-D671-3D14-AF8D-BA25E601F458> /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Ubiquity 0x9478e000 - 0x9478efff com.apple.Accelerate (1.8 - Accelerate 1.8) <4EC0548E-3A3F-310D-A366-47B51D5B6398> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate 0x9478f000 - 0x947c2ff5 libssl.0.9.8.dylib (47) <3224FBB3-3074-3022-AD9A-187703680C03> /usr/lib/libssl.0.9.8.dylib 0x94f5f000 - 0x94f69fff com.apple.speech.recognition.framework (4.1.5 - 4.1.5) <B855E8B4-2EE3-3BFF-8547-98A0F084F9AF> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition 0x94f6a000 - 0x94fc5ff7 com.apple.AppleVAFramework (5.0.19 - 5.0.19) <3C43A555-0A22-3D7C-A3FB-CFADDDA43E9B> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA 0x94fc6000 - 0x94fcdfff liblaunch.dylib (442.26.2) <310C99F8-0811-314D-9BB9-D0ED6DFA024B> /usr/lib/system/liblaunch.dylib 0x94fce000 - 0x9502cff7 com.apple.audio.CoreAudio (4.1.1 - 4.1.1) <953DD669-8C6E-387D-AB3F-D8C8965347DF> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio 0x9502d000 - 0x951b6ff7 com.apple.vImage (6.0 - 6.0) <1D1F67FE-4F75-3689-BEF6-4A46C8039E70> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage 0x951b7000 - 0x95275ff3 com.apple.ColorSync (4.8.0 - 4.8.0) <EFEDCB37-4F20-3CEC-A185-5D2976E11BAC> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync 0x95276000 - 0x956b8ff3 com.apple.CoreGraphics (1.600.0 - 331.0.4) <BC041647-FB5A-3D07-A253-F3D34E25BF6C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics 0x956b9000 - 0x957d1ff7 com.apple.coreavchd (5.6.0 - 5600.4.16) <F024C78B-4FAA-38F1-A182-AD0A0A596CBE> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD 0x957d2000 - 0x95872ff7 com.apple.QD (3.42 - 285) <1B8307C6-AFA8-312E-BA5B-679070EF2CA1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD 0x95873000 - 0x95ae0ffb com.apple.imageKit (2.2 - 670) <E5D08218-C9FC-32ED-B461-4725B2456404> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit 0x95e5a000 - 0x95e5dff3 com.apple.AppleSystemInfo (2.0 - 2) <4639D755-8A68-31C9-95C4-7E7F70C233FA> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo 0x95e5e000 - 0x95e5efff com.apple.Accelerate.vecLib (3.8 - vecLib 3.8) <908B8D40-3FB5-3047-B482-3DF95025ECFC> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib 0x95e6a000 - 0x95e6afff libSystem.B.dylib (169.3) <F479E729-89C7-3B4C-9731-678EB673A861> /usr/lib/libSystem.B.dylib 0x95eb1000 - 0x95ebdffe libkxld.dylib (2050.22.13) <ED37AAAA-B1C0-3ADF-A897-3D580A845843> /usr/lib/system/libkxld.dylib 0x95ebe000 - 0x95ec8ffe com.apple.bsd.ServiceManagement (2.0 - 2.0) <9732BA61-D6F6-3644-82DA-FF0D6FEEFC69> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement 0x95fc7000 - 0x95fd0ffe com.apple.aps.framework (3.0 - 3.0) <F4EF9C03-5B1B-3559-A77D-BD1B2D11167E> /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService 0x95fd1000 - 0x95fd7fff libGFXShared.dylib (8.7.25) <4268BFAF-4529-3B40-A8B9-66F176AC20CF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib 0x95fd8000 - 0x96073fff com.apple.CoreSymbolication (3.0 - 117) <F705A8CD-A04A-3A84-970A-7B04BC05DA97> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication 0x96074000 - 0x9617fff7 libJP2.dylib (849) <B2D0E844-C390-376C-91D9-F3501B5C7A83> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib 0x96180000 - 0x961b6ffb com.apple.DebugSymbols (98 - 98) <9A9ADA0A-E487-3C8F-9998-286EE04C235A> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols 0x961b7000 - 0x961e3ff7 libsystem_info.dylib (406.17) <AA5611DB-A944-3072-B6BE-ACAB08689547> /usr/lib/system/libsystem_info.dylib 0x961e4000 - 0x96219fff libTrueTypeScaler.dylib (84.6) <B7DB746B-7A61-38EF-8CA7-408ED9C14A02> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib 0x96257000 - 0x96575ff3 com.apple.Foundation (6.8 - 945.16) <C4D95341-B4FF-30AC-815A-A23C019C57A3> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation 0x96578000 - 0x965c2ff7 com.apple.framework.CoreWLAN (3.0.2 - 302.12) <1D7CB11D-C28C-3A25-865A-4AD6EE40D493> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN 0x965c3000 - 0x965d6ff9 com.apple.MultitouchSupport.framework (235.29 - 235.29) <451701B6-03CE-3F26-9FF0-92D8DA1467EE> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport 0x965d7000 - 0x96630fff com.apple.QuickLookFramework (4.0 - 555.5) <4E381B7B-7EB5-37FD-9BA7-517DB48D07A7> /System/Library/Frameworks/QuickLook.framework/Versions/A/QuickLook 0x96631000 - 0x9663afff com.apple.DiskArbitration (2.5.2 - 2.5.2) <89822A83-B450-3363-8E9C-9B80CB4450B1> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration 0x9663b000 - 0x9669dfff libc++.1.dylib (65.1) <C0CFF9FF-5D52-3EAE-B921-6AE1DA00A135> /usr/lib/libc++.1.dylib 0x9669e000 - 0x9669efff com.apple.ApplicationServices (45 - 45) <677C4ACC-9D12-366F-8A87-B898AC806DD9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices 0x96778000 - 0x96960ffb com.apple.CoreFoundation (6.8 - 744.18) <68AFEE40-0078-347E-9DEE-32CFE0062A10> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x96961000 - 0x96965ffe libcache.dylib (57) <834FDCA7-FE3B-33CC-A12A-E11E202477EC> /usr/lib/system/libcache.dylib 0x96966000 - 0x96967fff liblangid.dylib (116) <E13CC8C5-5034-320A-A210-41A2BDE4F846> /usr/lib/liblangid.dylib 0x96968000 - 0x96999fff com.apple.DictionaryServices (1.2 - 184.4) <0D5BE86F-F40A-3E39-8569-19FCA5EDF9D3> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices 0x9699a000 - 0x9699effc libGIF.dylib (849) <2F1DE1C6-4779-35A6-8ED5-BBF8ADD5962A> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib 0x9699f000 - 0x9702bff3 com.apple.CoreAUC (6.16.13 - 6.16.13) <3DCF4456-AF8D-3E87-B00C-C56055AF9B8E> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC 0x9706c000 - 0x97089fff libxpc.dylib (140.42) <1E419D55-C5C1-33FF-B52E-6C7FFBEA5E1F> /usr/lib/system/libxpc.dylib 0x9708a000 - 0x9708bfff libdnsinfo.dylib (453.19) <3B523729-84A8-3D0B-B58C-3FC185060E67> /usr/lib/system/libdnsinfo.dylib 0x97095000 - 0x97251ffd libicucore.A.dylib (491.11.2) <59A23F06-16AD-35F8-BA58-D17305232402> /usr/lib/libicucore.A.dylib 0x97252000 - 0x974f5ff3 com.apple.CoreImage (8.2.4 - 1.0.1) <BA4EE8D7-FE72-3CC3-801F-B69D8A8B426F> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage.framework/Versions/A/CoreImage 0x974f6000 - 0x978d9fff com.apple.HIToolbox (2.0 - 626.1) <ECC3F04F-C4B7-35BF-B10E-183B749DAB92> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox 0x978da000 - 0x97949ffb com.apple.Heimdal (3.0 - 2.0) <964D9952-B0F2-34F6-8265-1823C0D5EAB8> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal 0x979a1000 - 0x979aafff com.apple.CommerceCore (1.0 - 26.1) <8C28115C-6EC1-316D-9237-F4FBCBB778C5> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/CommerceCore.framework/Versions/A/CommerceCore 0x979ab000 - 0x97a05fff com.apple.ImageCaptureCore (5.0.2 - 5.0.2) <BB0D85EE-A85D-3E7B-B04E-720886553258> /System/Library/Frameworks/ImageCaptureCore.framework/Versions/A/ImageCaptureCore 0x97a06000 - 0x97a06ffd libOpenScriptingUtil.dylib (148.3) <87895E27-88E2-3249-8D0E-B17E76FB00C1> /usr/lib/libOpenScriptingUtil.dylib 0x97a07000 - 0x97a10ffd com.apple.audio.SoundManager (4.0 - 4.0) <ABC5FE40-B222-36EB-9905-5C8C4BFD8C87> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.framework/Versions/A/CarbonSound 0x97a11000 - 0x97a8aff0 com.apple.CorePDF (2.0 - 2) <6B5BF755-F336-359C-9A99-F006F61442CF> /System/Library/PrivateFrameworks/CorePDF.framework/Versions/A/CorePDF 0x97a8b000 - 0x97a98ff7 com.apple.AppleFSCompression (49 - 1.0) <166AA1F8-E50A-3533-A3B5-8737C5118CC3> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression 0x97a99000 - 0x97aabff7 libdispatch.dylib (228.23) <86EF7D45-2D97-3465-A449-95038AE5DABA> /usr/lib/system/libdispatch.dylib 0x97aac000 - 0x97d97ff7 com.apple.AOSKit (1.05 - 152.2) <9FDCE5E4-B68D-38F6-A5DB-D1597D5C4252> /System/Library/PrivateFrameworks/AOSKit.framework/Versions/A/AOSKit 0x97d98000 - 0x97d99ffd com.apple.TrustEvaluationAgent (2.0 - 23) <E42347C0-2D3C-36A4-9200-757FFA61B388> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent 0x97d9d000 - 0x97d9efff libquarantine.dylib (52) <D526310F-DC77-37EA-8F5F-83928EFA3262> /usr/lib/system/libquarantine.dylib 0x97d9f000 - 0x97df9fff com.apple.Symbolication (1.3 - 93) <A839CFC2-F870-3652-B353-15A55D88F88D> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication 0x97dfa000 - 0x97dfdff9 libCGXType.A.dylib (331.0.4) <981B13D6-4E8B-3468-92D3-FE436B48C0DA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib 0x97dfe000 - 0x97eb5ff3 com.apple.QuickTimeMPEG4.component (7.7.1 - 2599.24) <E79C5B16-E004-33C2-B5C0-17AD66F283E3> /System/Library/QuickTime/QuickTimeMPEG4.component/Contents/MacOS/QuickTimeMPEG4 0x97eb6000 - 0x97eedffa com.apple.LDAPFramework (2.4.28 - 194.5) <B7BAC5B9-ABA9-3799-B8B5-D2DED9383C24> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP 0x97eee000 - 0x97f13ff7 com.apple.CoreVideo (1.8 - 99.4) <A26DE896-32E0-3D5E-BA89-02AD23FA96B3> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo 0x97f14000 - 0x97fc8fff com.apple.coreui (2.0 - 181.1) <C15ABF35-B7F5-34ED-A461-386DAF65D96B> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI 0x97fc9000 - 0x98018ff6 libTIFF.dylib (849) <229EBA67-A2D3-30B7-8177-3CA5503360EC> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib 0x98019000 - 0x980fafff libcrypto.0.9.8.dylib (47) <D4EFFCFB-206D-3E3D-ADB5-CBAF04EB8838> /usr/lib/libcrypto.0.9.8.dylib 0x980fb000 - 0x98102fff libsystem_dnssd.dylib (379.37) <49A44FB3-559D-3C7E-AA40-23F5A8E612AC> /usr/lib/system/libsystem_dnssd.dylib 0x98103000 - 0x9814bff5 com.apple.opencl (2.2.18 - 2.2.18) <004A1DE4-49C6-3938-8B54-CD1DC23BDBE5> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL 0x9817d000 - 0x98186ff9 com.apple.CommonAuth (3.0 - 2.0) <34C4768C-EF8D-3DBA-AFB7-09148C8672DB> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth 0x9818b000 - 0x981b4fff libxslt.1.dylib (11.3) <0DE17DAA-66FF-3195-AADB-347BEB5E2EFA> /usr/lib/libxslt.1.dylib 0x981b5000 - 0x981b7ffd libCVMSPluginSupport.dylib (8.7.25) <C8FC6227-5209-3138-89CD-03CAD11F3EC3> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib 0x981b8000 - 0x981d1fff com.apple.Kerberos (2.0 - 1) <9BDE8F4D-DBC3-34D1-852C-898D3655A611> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos 0x981d2000 - 0x98565ff3 com.apple.MediaToolbox (1.0 - 926.87) <F3623474-03AD-3A7F-8BD1-46A44A12E74E> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox 0x98604000 - 0x98619fff com.apple.speech.synthesis.framework (4.1.12 - 4.1.12) <DE68CEB5-4959-3652-83B8-D2B00D3B932D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis 0x9861a000 - 0x98718ff7 libFontParser.dylib (84.6) <7D3EB3CC-527E-3A74-816A-59CAFD2260A4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib 0x98765000 - 0x987f7ffb libvMisc.dylib (380.6) <6DA3A03F-20BE-300D-A664-B50A7B4E4B1A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib 0x987f8000 - 0x9883aff7 libcups.2.dylib (327.3) <C7A4A315-FA15-354B-8BC9-BE824C4EFF6D> /usr/lib/libcups.2.dylib 0x9883b000 - 0x9883bfff com.apple.Cocoa (6.7 - 19) <354094F0-F36B-36F9-BF5F-FD60590FBEB9> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa 0x9883c000 - 0x988a4ff7 com.apple.framework.IOKit (2.0.1 - 755.22.5) <F9A70D23-1108-3616-9DE3-6C5730CA7AB2> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit 0x988a5000 - 0x988cfff9 com.apple.framework.Apple80211 (8.3.2 - 832.18.1) <69AD5C5E-14A2-3E2B-AE28-2C7A7E4F5D0A> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211 0x988d0000 - 0x98936fff com.apple.print.framework.PrintCore (8.3 - 387.2) <0F7665F5-33F0-3661-9BE2-7DD2890E304B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore 0x98937000 - 0x9896affb com.apple.GSS (3.0 - 2.0) <9566A96D-C296-3ABD-A12A-E274C81C0B25> /System/Library/Frameworks/GSS.framework/Versions/A/GSS 0x98a0d000 - 0x98b1dff3 com.apple.QuickTimeImporters.component (7.7.1 - 2599.24) <3DBEE5E4-4C40-3390-8405-0D9E271084B2> /System/Library/QuickTime/QuickTimeImporters.component/Contents/MacOS/QuickTimeImporters 0x98b1e000 - 0x98db8fff com.apple.AddressBook.framework (7.1 - 1169) <AF50144A-A327-3367-81B1-95B3D46E56F0> /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook 0x98db9000 - 0x98dc7ff3 libsystem_network.dylib (77.10) <7FBF5A15-97BA-3721-943E-E77F0C40DBE1> /usr/lib/system/libsystem_network.dylib 0x98dc8000 - 0x98f16fff com.apple.CFNetwork (596.3.3 - 596.3.3) <EC7EF37B-B00E-374D-9E8F-E4E22D741059> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork 0x98f17000 - 0x98f1dfff com.apple.print.framework.Print (8.0 - 258) <12AEAD24-6924-3923-9E4A-C5D21231E639> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print 0x98f1e000 - 0x98f9affb libType1Scaler.dylib (101.1) <0D94D786-29F7-33DB-B64B-B264FA5EACD2> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libType1Scaler.dylib 0x98f9b000 - 0x98f9bfff com.apple.vecLib (3.8 - vecLib 3.8) <83160DD1-5614-3E34-80EB-97041016EF1F> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib 0x98f9c000 - 0x98fb9ff7 libresolv.9.dylib (51) <B9742A2A-DF15-3F6E-8FCE-778A58214B3A> /usr/lib/libresolv.9.dylib 0x98fba000 - 0x98fd1fff com.apple.GenerationalStorage (1.1 - 132.3) <DD0AA3DB-376D-37F3-AC5B-17AC9B9E0A63> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage 0x98fd2000 - 0x9914aff5 com.apple.QuartzCore (1.8 - 304.2) <FB737C74-C460-32A3-9107-D2112BAE6EBC> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore 0x9914b000 - 0x991f5fff com.apple.LaunchServices (539.7 - 539.7) <AF33EBD3-BC0B-30B5-B7DA-5CCCF12D7EDD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices 0x991f6000 - 0x99223ffb com.apple.CoreServicesInternal (154.2 - 154.2) <DCCF604B-1DB8-3F09-8122-545E2E7F466D> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal 0x99253000 - 0x9928efef libGLImage.dylib (8.7.25) <6C0B2148-032A-3911-AB21-2E07606E3D9A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib 0x99291000 - 0x9937aff7 libxml2.2.dylib (22.3) <015A4FA6-5BB9-3F95-AFB8-B9281E22685B> /usr/lib/libxml2.2.dylib 0x9937b000 - 0x9937bfff com.apple.Carbon (154 - 155) <C0A26E7B-28F1-3C7E-879E-A3CF3ED5111C> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon 0x9937c000 - 0x99395ffb com.apple.frameworks.preferencepanes (15.1 - 15.1) <D788C8BE-5A13-3EA3-93FA-9B5CEEFE249B> /System/Library/Frameworks/PreferencePanes.framework/Versions/A/PreferencePanes 0x99396000 - 0x993bafff com.apple.PerformanceAnalysis (1.16 - 16) <18DE0F9F-1264-394D-AC56-6B2A1771DFBE> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis 0x993bb000 - 0x99518ffb com.apple.QTKit (7.7.1 - 2599.24) <39CC892D-2874-33FE-BE30-87FE07D875BD> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit 0x99519000 - 0x9951dff7 libmacho.dylib (829) <5280A013-4F74-3F74-BE0C-7F612C49F1DC> /usr/lib/system/libmacho.dylib 0x9951e000 - 0x99520fff com.apple.securityhi (4.0 - 55002) <79E3B880-3AB7-3BF3-9CDF-117A45599545> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI 0x99521000 - 0x99545fff libJPEG.dylib (849) <CD42C17E-6B13-35BE-B585-9AE69CEA534F> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib 0x99546000 - 0x9963aff3 com.apple.QuickLookUIFramework (4.0 - 555.5) <5A62C87F-5F74-380B-8B86-8CE3D8788603> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/QuickLookUI 0x9963b000 - 0x9967fff7 libGLU.dylib (8.7.25) <0CC1A4D8-C095-3F2B-B55C-FDEBEA0E9CFE> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib 0x99680000 - 0x99a38ffa libLAPACK.dylib (1073.4) <9A6E5EAD-F2F2-3D5C-B655-2B536DB477F2> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib 0x99a39000 - 0x99b2affc libiconv.2.dylib (34) <B096A9B7-83A6-31B3-8D2F-87D91910BF4C> /usr/lib/libiconv.2.dylib 0x99b2b000 - 0x99c5eff3 com.apple.MediaControlSender (1.7 - 170.20) <7B1AC317-AFDB-394F-8026-9561930E696B> /System/Library/PrivateFrameworks/MediaControlSender.framework/Versions/A/MediaControlSender 0x99c5f000 - 0x9a05bfeb com.apple.VideoToolbox (1.0 - 926.87) <D6460276-E1CF-317D-B32F-80EAE916168C> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox 0x9a05c000 - 0x9a076ffc libsystem_kernel.dylib (2050.22.13) <70C520E8-0394-3DFB-823B-FE8C251C169A> /usr/lib/system/libsystem_kernel.dylib 0x9a077000 - 0x9a10eff7 com.apple.ink.framework (10.8.2 - 150) <D90FF7BC-6B90-39F1-AC52-670269947C58> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink 0x9a10f000 - 0x9a110fff libremovefile.dylib (23.2) <9813B2DB-2374-3AA2-99B6-AA2E9897B249> /usr/lib/system/libremovefile.dylib 0x9a111000 - 0x9a196ff7 com.apple.SearchKit (1.4.0 - 1.4.0) <454E950F-291C-3E95-8F35-05CA0AD6B327> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit 0x9a197000 - 0x9a19ffff libcopyfile.dylib (89) <4963541B-0254-371B-B29A-B6806888949B> /usr/lib/system/libcopyfile.dylib 0x9a1a0000 - 0x9a3d0fff com.apple.QuartzComposer (5.1 - 284) <4E8682B7-EBAE-3C40-ABDB-8705EC7952BD> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzComposer.framework/Versions/A/QuartzComposer 0x9a3d1000 - 0x9a412ff7 com.apple.framework.CoreWiFi (1.2.2 - 122.12) <D9479FFE-2D79-373C-9F73-E746664ACD5C> /System/Library/Frameworks/CoreWiFi.framework/Versions/A/CoreWiFi 0x9a413000 - 0x9a461ffb libFontRegistry.dylib (100) <3B8350C2-4D8F-38C4-A22E-2F855D7E83D1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib 0x9a464000 - 0x9a4a9ff7 com.apple.NavigationServices (3.7 - 200) <F6531764-6E43-3AF3-ACDD-8A5551EF016A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationServices.framework/Versions/A/NavigationServices 0x9a4aa000 - 0x9a504ffb com.apple.AE (645.6 - 645.6) <44556FF7-A869-399A-AEBB-F4E9263D9152> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE 0x9a505000 - 0x9a5d9ff3 com.apple.backup.framework (1.4.2 - 1.4.2) <0473EB45-E9BF-3C10-B235-A6E2B960A88F> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup 0x9a5da000 - 0x9a5ecfff libbsm.0.dylib (32) <DADD385E-FE53-3458-94FB-E316A6345108> /usr/lib/libbsm.0.dylib 0x9a5ed000 - 0x9a622ff7 com.apple.framework.internetaccounts (2.1 - 210) <553BF1E7-B26F-3BE7-BAA9-D80E53E73B0D> /System/Library/PrivateFrameworks/InternetAccounts.framework/Versions/A/InternetAccounts 0x9a623000 - 0x9a62affb libunwind.dylib (35.1) <E1E8D8B3-3C78-3AB1-B398-C180DC6DCF05> /usr/lib/system/libunwind.dylib 0x9a62b000 - 0x9a637ffa com.apple.CrashReporterSupport (10.8.3 - 417) <A4A45B14-8992-3739-82BC-3C5E5C2686F9> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport 0x9a63c000 - 0x9a67effb com.apple.RemoteViewServices (2.0 - 80.6) <AE962502-4539-3893-A2EB-9D384652AEAC> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices 0x9a67f000 - 0x9a69bfff libPng.dylib (849) <BF2CB6F5-A2F1-35A4-93F7-ACA6D7F02084> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib 0x9a69c000 - 0x9a6a8ff7 com.apple.NetAuth (4.0 - 4.0) <4983C4B8-9D95-3C4D-897E-07743326487E> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth 0x9a6a9000 - 0x9a6d6ffe libsystem_m.dylib (3022.6) <9975D9C3-3B71-38E3-AA21-C5C5F9D9C431> /usr/lib/system/libsystem_m.dylib 0x9a6d7000 - 0x9a74cff7 com.apple.ApplicationServices.ATS (332 - 341.1) <95206704-F9C9-33C4-AF25-FE9890E160B2> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS

External Modification Summary:

Calls made by other processes targeting this process:

task_for_pid: 2 thread_create: 0 thread_set_state: 0

Calls made by this process:

task_for_pid: 0 thread_create: 0 thread_set_state: 0

Calls made by all processes on this machine:

task_for_pid: 1896 thread_create: 2 thread_set_state: 0

VM Region Summary: ReadOnly portion of Libraries: Total=206.0M resident=127.6M(62%) swapped_out_or_unallocated=78.4M(38%) Writable regions: Total=115.6M written=2956K(2%) resident=19.4M(17%) swapped_out=1544K(1%) unallocated=96.2M(83%) REGION TYPE VIRTUAL =========== ======= ATS (font support) 32.9M ATS (font support) (reserved) 4K reserved VM address space (unallocated) CG backing stores 9652K CG raster data 56K CG shared images 1216K CoreServices 2000K IOKit 8K MALLOC 43.8M MALLOC guard page 48K Memory tag=240 4K Memory tag=242 12K Memory tag=249 156K Memory tag=35 2456K Stack 66.5M VM_ALLOCATE 16.2M DATA 11.8M DATA/OBJC 272K IMAGE 528K IMPORT 16K LINKEDIT 39.1M OBJC 2964K OBJC/DATA 48K PAGEZERO 4K TEXT 166.9M UNICODE 544K mapped file 72.0M shared memory 308K =========== ======= TOTAL 469.1M TOTAL, minus reserved VM space 469.1M

Model: MacBookPro8,1, BootROM MBP81.0047.B27, 2 processors, Intel Core i5, 2.4 GHz, 4 GB, SMC 1.68f99 Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 384 MB Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020 Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.100.16) Bluetooth: Version 4.1.3f3 11349, 2 service, 11 devices, 1 incoming serial ports Network Service: Wi-Fi, AirPort, en1 Serial ATA Device: TOSHIBA MK5065GSXF, 500.11 GB Serial ATA Device: MATSHITADVD-R UJ-8A8 USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfa100000 / 3 USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0xfa120000 / 5 USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4 USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821a, 0xfa113000 / 8 USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0xfa200000 / 2 USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfd100000 / 2 USB Device: GT-I9082, 0x04e8 (Samsung Electronics Co., Ltd.), 0x6865, 0xfd120000 / 4 USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3

I use FileZilla 3.5.2 on a Linux Mint 12 (Lisa) plattform to connect to my Samsung Galaxy S2 Smartphone with Android 2.3 and the latest version of the App "Software Data Cable", which provides an FTP server for my phone's file system in my home network (over WLAN).

I can connet to the server without any problems, browse through the server file system and all folders and files are displayed correctly. However, when I want to download the content of my camera folder (about 100 JPEG-photos and 40 .mp4 video files) by marking all the files (click on first, Shift-click on the last file to be copied) and dragging them from the server folder window into the local folder window, Filezilla crashes.

I have attatched the Filezilla message log (file: "filezilla.log") which records the output from the launch up to the point when I opened the folder containing the files to download. When I dragged them over to my home folder the program crashed without any further output.

In addition to that I added a more useful log file from the gdb debugger, which shows the segmentation fault at the point of the crash. (file name: "filezilla crash.log")

I am running the Ubuntu 11.10 (Oneiric) based "Linux Mint 12" (Lisa) 64-bit on an Acer TravelMate 5740G Notebook with an Intel Core i5-430M and an ATI Mobility Radeon 5650 (using the proprietary fglrx driver for it). I also use the proprietary driver for the Broadcom WLAN card (package name is simply "wlan").

FileZilla Client

Version: 3.5.2

Build information:

Compiled for: x86_64-pc-linux-gnu Compiled on: x86_64-pc-linux-gnu Build date: 2011-11-09 Compiled with: gcc (Ubuntu 4.4.3-4ubuntu5) 4.4.3 Compiler flags: -g -O2 -Wall -g -fexceptions -std=gnu++0x

Linked against:

wxWidgets: 2.8.10 GnuTLS: 2.10.5

Operating system:

Name: Linux 3.0.0-12-generic x86_64 Version: 3.0

Anytime i right mouse click in FileZilla it crashes the program and displays the following message ?

Error Signature AppName: filezilla.exe AppVer: 3.3.4.1 ModName: oleacc.dll ModVer: 4.2.5406.0 Offset: 0001e368

FileZilla v3.1.5.1 seems to have a problem uploading Entire file trees.

on an attempt to upload a folder tree, I dragged and dropped the base folder of a wordpress plugin in FileZilla. The base folder and immediate sub-folders were transferred, with the files they contain. However, any folders further down the tree were not transferred.

In reference to the attached screenshot, the highlighted folder was the one I dragged and dropped (from local window in FZ to server window in FZ). The sub-folders marked in green were sucessfully transferred with the files contained. The folders further down the tree marked in red were not transferred.

The fault is consistent on my system, but has not ocurred in previous versions of FileZilla.

System spec HP 8510w Mobile Workstation (laptop)(nVidia QuadroFX 570m graphics card, intel Core2 Duo T7700, 4 GB RAM) Running english Windows Vista x64 SP1

Anytime I use FileZilla for moving a decent amount of files or largely sized files it just Times Out and won't get another good connection. This has been happening for the past 6 months, I should've reported sooner but I kept thinking it was fixed everytime I saw a fresh update. It's happened over various OS X versions as they keep making newer ones. It seems touchy and I haven't quite figured out how to fix this in a bypass sort of way.

So let's say I want to download a 1GB file from one of my servers, it is working just fine and then when it may get to, let's say, 40% it just pauses. Then it says Timed Out, continues to attempt reconnecting but fails. Some ways I've bypassed it have been: -Waiting 10 minutes to almost a week -Unprocessing the Queue and waiting, then Process it again -Disconnect, and waiting, then Reconnect -Restarting FileZilla Restarting my computer doesn't seem to fix it, as well as re-installing FileZilla, and I've also triedwiping the server data. This has happened on at least 4 seperate servers for me. And not all of the above work, like previously stated it's a weird bug and seems touchy. Some require multiple of the above to happen, sometimes it just takes a whole lot of time.

The servers run on professional hosts and have not reported any issues or downtimes and did not see why it was happening to me. I have spoken to other users on Windows and they haven't had issues using my servers.

Connecting to probe.filezilla-project.org Response: 220 FZ router and firewall tester ready USER FileZilla Response: 331 Give any password. PASS 3.9.0.4 Response: 230 logged on. Checking for correct external IP address IP 71.179.248.34 hb-bhj-cei-de Response: 200 OK PREP 1033 Response: 200 Using port 1033, data token 28798304 PORT 71,179,248,34,4,9 Connection closed

Attempting to set up FileZilla with settings: Passive, External IP, Use the following IP Address, Use the following port range, and I get that error. PLease help!

Hi,

This morning I noticed that my private key authentication, which used to work seamlessly, is now frequently timing out. When it doesn't time out, it's taking a very long time to successfully process actions such as directory changes or file updates. My initial thought is that this might be related to the notification in my FileZilla that a new version is available. However, there doesn't appear to be a valid version available for my operating system.

I already tried making new connections to my web server. When that didn't help, I quit and restarted FileZilla, which also didn't help.

When trying to connect to non default ports it will work if you use HOST:PORT, but not if you put the port in the "Port" textbox, whether I use Quickconnect or a pre-defined server, both ignore the port.

Each time I close FileZilla, the app is not completely closed. Each time one more process remains in Windows Task Manager. Sometimes there are 10 or even more similar processes running in the background.

The prevents me from installing any FileZilla update. I always need to abort a number of processes before being able to update.

The first time I run FileZilla after having updated FileZilla or having rebooted the computer, an error message occurs something like «Last time FileZilla did not exit properly and needs to be cleaned up. Please try again.»

This is annoying. I hope this can be fixed. Thank you.

Here is the message I get when trying to download the new version.

Started update check on 2018-08-22 09:41:45 Own build type: official Downloading update.filezilla-project.org/update.php?platform=x86_64-w64-mingw32&version=3.32.0&product=3&osversion=10.0&osarch=64&updated=1&cpuid=sse,sse2,sse3,ssse3,sse4.1,sse4.2,avx,avx2,aes,pclmulqdq,rdrnd,bmi2,bmi2,adx&initial=0 Resolving address of update.filezilla-project.org Connecting to 136.243.154.122:443... Connection established, initializing TLS... Verifying certificate... TLS connection established, sending HTTP request File transfer successful, transferred 1,475 bytes in 1 second Parsing 1475 bytes of version information. Found new release 3.35.2 Downloading /FileZilla_Pro_3.35.2_win64-setup.exe Resolving address of download.filezilla-project.org Connecting to 136.243.154.86:443... Connection established, initializing TLS... Verifying certificate... TLS connection established, sending HTTP request Resolving address of prodownload.filezilla-project.org Connection timed out after 20 seconds of inactivity File transfer failed

Hi,

I just updated to the latest version 3.45.1 and now unable to access Google's Shared Drives. *Checked accessibility via web browser, works OK.

This is what I've tried a few times after restarting.

1. Connecting to Google Drive is per usual
2. Accessing "My Drive" (personal) and "Shared with Me" works normally.
3. When I click into Shared Drives, and I click on one of the Shared Drives subfolders, FileZilla Pro becomes unresponsive/frozen.
4. Upon freezing, I'm unable to click on anything except to close it.

<Laptop and FileZilla info>

FileZilla Pro

Version: 3.45.1

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2019-09-25 Compiled with: x86_64-w64-mingw32-gcc (GCC) 8.3-win32 20190406 Compiler flags: -g -O2 -Wall

Linked against:

wxWidgets: 3.0.5 SQLite: 3.29.0 GnuTLS: 3.6.9

Operating system:

Name: Windows 10 (build 17763), 64-bit edition Version: 10.0 Platform: 64-bit system CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi2 bmi2 adx lm Settings dir: C:\Users\howie\AppData\Roaming\FileZilla\

<Message Log>

Status: Resolving address of www.googleapis.com Status: Connecting to [2404:6800:4001:80e::200a]:443... Status: Connection established, initializing TLS... Status: Verifying certificate... Status: TLS connection established, sending HTTP request Status: Retrieving root listing... Status: Directory listing of "/" successful Status: Retrieving directory listing of "/My Drive"... Status: Directory listing of "/My Drive" successful Status: Retrieving directory listing of "/Shared with me"... Status: Directory listing of "/Shared with me" successful Status: Retrieving directory listing of "/Shared drives"... Status: Directory listing of "/Shared drives" successful Status: Retrieving directory listing of "/Shared drives/howie Shuttle"...

Hi,

I have multiple OneDrive accounts, but after connecting to one, it seems I cannot disconnect from it, as trying to connect to the second account automatically connects me with the first one.

This is not desired.

FileZilla Pro

Version: 3.42.0

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2019-05-05 Compiled with: x86_64-w64-mingw32-gcc (GCC) 6.3.0 20170516 Compiler flags: -g -O2 -Wall

Linked against:

wxWidgets: 3.0.5 SQLite: 3.26.0 GnuTLS: 3.6.7

Operating system:

Name: Windows 10 (build 17763), 64-bit edition Version: 10.0 Platform: 64-bit system CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx aes pclmulqdq bmi2 lm Settings dir: C:\Users\[redacted]\AppData\Roaming\FileZilla\

Thanks, Robin

02 May - please see attached file. FileZilla is not working on my machine & IT and cybersecurity have exhausted all options.

I downloaded FileZilla Pro earlier this week and had NO issues with it until yesterday. I kept getting the "421 Proxy is closed" error. I upgraded to the newest version of FileZilla yesterday, checked all my network connections, etc. and roped in IT--they couldn't find any issues and were already allowing the app. I've run every diagnostic and nothing is working. Like I mentioned before, I don't have an IT background & have tried just about everything. Any suggestions? Below is the message log...

Status: Connecting to <server name>... Response: fzSftp started, protocol_version=11 Command: open "<server name>" 22 Error: Connection timed out after 20 seconds of inactivity Error: Could not connect to server Status: Disconnected from server Status: Resolving address of <server name> Status: Connecting to 52.227.72.32:21... Status: Connection established, waiting for welcome message... Response: 421 Proxy is closed Error: Could not connect to server Status: Waiting to retry... Status: Resolving address of <server name> Status: Connecting to 52.227.72.32:21... Status: Connection established, waiting for welcome message... Response: 421 Proxy is closed Error: Could not connect to server Top

Hi Guys, I start having a weird problem uploading to webdav. It was working before but now when I upload folders it shows that it transfers/transfers is complete and not showing as failed/, but there is no folders nor files in the remote drive. At the same time if i manually make the folder on the remote drive and upload only files into it works just fine. I made a screen video to show you how it acts.

Enter in host name, user, password. The credentials are still being sent to Amazon and not the host name I entered.

Filezilla Pro version 3.28.0

Windows 7 Pro.

Ever since last update, it always takes 2 tries to rename a file.

1st try does nothing. 2nd try always successful.

OS: Windows 10

I recently upgraded to FileZilla 3.9.0.2. Every time I start it up and use the Site Manager to connect, I get 1 and sometimes 2 copies of a popup window with the following error: File 'C:\Users\Karen\AppData\Roaming\FileZilla\filezilla.xml~' couldn't be removed (error 0: the operation completed successfully.) Each popup window is accompanied by a loud warning sound; each has to be cleared separately before I can do anything else. They also sometimes pop up when I merely open Site Manager. I also sometimes see the popup when I close the client. I attach a screen shot of the error popup. Other than this, FileZilla client seems to operate normally. I started a connection (during which I got 2 popups) and copied the message log: Status: Connecting to 50.63.140.27... Response: fzSftp started Command: open "hedera@50.63.140.27" 22 Command: Pass: Status: Connected to 50.63.140.27 Status: Retrieving directory listing... Command: pwd Response: Current directory is: "/var/www/vhosts/lifering.org" Command: ls Status: Listing directory /var/www/vhosts/lifering.org Status: Calculating timezone offset of server... Command: mtime "pd" Response: 1407027289 Status: Timezone offsets: Server: -25200 seconds. Local: -25200 seconds. Difference: 0 seconds. Status: Directory listing successful This doesn't look helpful to me but maybe it'll help you. I've been running FileZilla literally for years and have never seen this before.

I have my task bar attached to the top of my screen. When FileZilla opened the first time, the top of the FileZilla window was obstructed by the task bar (see the screenshot). In order to move the window, I have to unlock the task bar and then shrink it to uncover the menu bar of FileZilla.

I have my task bar attached to the top of my screen. When FileZilla opened the first time, the top of the FileZilla window was obstructed by the task bar (see the screenshot). In order to move the window, I have to unlock the task bar and then shrink it to uncover the menu bar of FileZilla.

FileZilla is a very efficient file mover. However, there is a problem of time stamp marking where the moved file has the "modified" date as the current date instead of the original "modified" date of the file being moved. This problem occurs with the FileZilla menu selection "Preserve timestamps of transferred files" activated.

For reference, the Windows 10 copy and robocopy utilities preserve both the "modified" and "created" dates.

This FileZilla operation causes my backup operations using robocopy to needlessly copy files that are already up-to-date.

I've attached three file properties screen shots - 1) the original file; 2) the FileZilla upload; and 3) the robocopy upload. Notice the time stamps of the original and robocopy file are identical while the FileZilla file has a different "Created" date

For some reason uploads start to fail soon as the successful transfer count reaches 14,385 (or close to this number).

This happens both when a large directory holding in excess of 14,385 files is uploaded and also when several smaller uploads totalling more than 14,385 files are uploaded.

The only way I have found around this is to pause the upload when the successful upload count gets close to 14,300 then shutdown FileZilla to clear the successful transfer log count, re-open FileZilla and resume the transfer of files in the queue.

If there is a way around this I will appreciate someone telling me.

Thank you.

Paul

With Version 3.8.0 FileZilla will become unresponsive and cease file transfers - the process has to be terminated via task manager (Windows 7) - I have had to roll back to 3.7.4.1 - with this version I experience no issues whatsoever.

Filezilla 3.0.5.2 is disconnecting even with keep alive enabled. FZ 3.0.7 is not exhibiting this problem. I have had to revert to 3.0.7.

I have downloadet the latest release, and again it freeze when I opload 100 Mb and over, I have to restart my system the hard way, but when I lock in to the remote server the file is there anyway. It semes to be a Vista(64) problem, because it works fine on XP.

(Sorry about my english, I did my best)

I am using FileZilla 3.0.1 for OS X. Everytime a window opens in FileZilla (Site Manager, Options, Overwrite File), the main FileZilla window moves almost off the screen. When I close the option window, I then have to move the main window back.

The default FileZilla and Flash CS3 icon look too similar and are hard to distinguish when clicking around fast. It would be great if something could be done to distinguish it. See attached.

Just tried to build FileZilla 3.26.2 with libfilezilla 0.9.2 using GCC 5.3.0 and GNU Binutils 2.28 - got the following linkage error:

  CXXLD    filezilla
filezilla-asksavepassworddialog.o: In function `CAskSavePasswordDialog::OnOk(wxCommandEvent&)':
/home/elijah/rpmbuild/BUILD/filezilla-3.26.2/src/interface/asksavepassworddialog.cpp:50: undefined reference to `fz::random_bytes(unsigned int)'
filezilla-password_crypto.o: In function `private_key::generate()':
/home/elijah/rpmbuild/BUILD/filezilla-3.26.2/src/interface/password_crypto.cpp:40: undefined reference to `fz::random_bytes(unsigned int)'
/home/elijah/rpmbuild/BUILD/filezilla-3.26.2/src/interface/password_crypto.cpp:45: undefined reference to `fz::random_bytes(unsigned int)'
settings/filezilla-optionspage_interface.o: In function `COptionsPageInterface::SavePasswordOption()':
/home/elijah/rpmbuild/BUILD/filezilla-3.26.2/src/interface/settings/optionspage_interface.cpp:113: undefined reference to `fz::random_bytes(unsigned int)'
collect2: error: ld returned 1 exit status

Command

[elijah@santiago .libs]$ strings libfilezilla.so.0.0.0 | grep random_bytes

shows me the following output:

_ZN2fz12random_bytesEj
random_bytes
_ZN2fz12random_bytesEj

FileZilla configure script fails because it can't find libgnutls-config

I do have gnutls-2.10.4 installed but it doesn't come with libgnutls-config anymore

Could you please fix FileZilla build process so it doesn't look for libgnutls-config?

thanks for a great tool!

At least on Unix file systems (I didn't try Windows) FileZilla has problems, when the first character of a directory name is a blank. You can rename "/xy/testdir" to "/xy/ testdir" with FileZila and "/xy/ testdir" is shown correctly. But after refreshing, it is shown as:"/xy/testdir" and can not be accessed with FileZilla any more or in any way. You get: Error: Directory /testdir: no such file or directory Error: Failed to retrieve directory listing

This is correct, but does not help :)

It is not an issue of the Unix filesystem, because with other FTP-clients (e.g. WS_FTP Professional) everything works fine.

You may ask, why the hell is someone using one or more leading blanks in folder names. OK, I have to do it, but can't do it with FileZilla, so I had to change to another FTP client. Please fix this, Thanks!

Content of FileZilla Info:

FileZilla Client

Version: 3.19.0

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-unknown-linux-gnu Build date: 2016-06-27 Compiled with: x86_64-w64-mingw32-gcc (GCC) 4.9.1 Compiler flags: -g -O2 -Wall -g -std=gnu++14

Linked against:

wxWidgets: 3.0.3 GnuTLS: 3.4.10 SQLite: 3.11.1

Operating system:

Name: Windows 10 (build 10586), 64-bit edition Version: 10.0 Platform: 64-bit system CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx aes pclmulqdq rdrnd Settings dir: C:\Users\Gintz\AppData\Roaming\FileZilla\

Hello, FileZilla Team (I'm from Switzerland, so my english may be bad) If I connect with FileZila to 213.251.167.117:21 (public server) He gives me a List of four Directories, I can only access the Directory named "1" with clicking on it, my network capture toool told me, that the inaccessible Dirs contain some spaces at the Beginning or the end of the name (and one subdirectory is only named with a space, but by entering / / into the ), by entering the name manually I can access the Directory and the Files in it. As an attachment, I give you the result from my network capturing tool, in the Window you can see the Hex and ASCII output, on the Bottom, again, ASCII (but with line breaks like in Notepad) Hope this Information helps to solve this issue

Trying to update FileZilla from 3.46.3 to 3.56 on MacOS 10.15.7. Downloaded installer FileZilla_3.56.0_macosx-x86.app.tar.bz2. Unpacked it using WinZip, in Downloads folder. Double-clicking on the FileZilla.app icon gets this message: The application “FileZilla.app” can’t be opened. Version 3.46.3 works fine. I tried renaming ~/.config/filezilla (rather than deleting it), but it did not help. I checked, but did not find a ticket about this problem. Advice? Thank you, Stan Hendryx, stanhx@…

When I edit my settings and click save, I get an error about the program not being able to locate Notepad on Windows 11. I can see the options menus until I click save and then it just gives me the error.

I would like to re-open this ticket. ​http://trac.filezilla-project.org/ticket/5210

Three years ago it is claimed this was a "rejected ticket." And yet the exact same problem still exists.

"To solve this issue, simply upgrade to a modern server supporting the MLSD command o refrain from using leading spaces."

This is not true. Even servers completely up to date still have the problem with leading spaces and files that cannot be transferred. The main question is how come I can log into the same server with ANY OTHER FTP PROGRAM and the file will transfer perfectly. But using FileZilla and the files are displayed incorrectly and the transfer FAILS. I don't think this bug should just be rejected. IT IS A BUG THAT SHOULD BE FIXED!

I'm using version 3.6.0.1 and I don't see how someone can say this isn't really a bug when ALL other programs handle these files perfectly. Why can't FileZilla???

Please someone fix this! It is very annoying finding 50 files with leading spaces and then having to load up another ftp program and transfer each file manually... Thank you to whoever fixed this!!!!!

SOFT: FileZilla Portable v3.5.3 OS : Windows 7 x64, Aero, Intel G45, all is updated CASE:

Open FileZilla Client, all is OK. Connect to one site, error occure. the [Message Log] panel's rendering exceed its Border. It will damage the UI of Menu/Toolbar/QuickConnBar and even the LocalDir panel.

TRY:

I have test FileZilla Portable on Windows XP with same config/Data, no this error.

v3.16.1 gives an update for 3.17.0.1, even with the "check for update"-setting disabled. I am often abroad on a mobile pay-per-byte connection, and both dialog and mobile data costs pretty annoying.

I am aware of the general rule to install the latest version and try again before reporting the bug, which would ofcourse ' ' ' solve ' ' ' the problem as in not showing that there's a newer version.

My config (relevant sections):

<Setting name="Update Check">0</Setting> <Setting name="Update Check Interval">7</Setting> <Setting name="Last automatic update check">2016-05-16 23:01:59</Setting> <Setting name="Update Check New Version">nightly 2016-05-09 ​http://filezilla-project.org/nightlies/2016-05-09/x86_64-w64-mingw32/FileZilla_3_setup.exe 7088584 sha512 4c0b208c0d37cf4c0e24bea9dde489c0a6485692b2bf13b770769b4d7c7213d05af9110319d6f9ab73cdbd105bb95d3eb3fe60e69bd01307077d8c7bb98d23f4

release 3.17.0.1 ​http://downloads.sourceforge.net/filezilla/FileZilla_3.17.0.1_win64-setup.exe 6513888 sha512 4d5e5d426af9dd689cb8c070d528c849719dc18544de194475bf3a0f5e35f8c9d449749fb2074a68292579b267ee2b23d1e2b31bae20d7185aa44061cca6981c

3.17.0.1 (2016-05-09) ... I removed 'whatsnew' items for bug report brevity ... </Setting>

<Setting name="Update Check Check Beta">0</Setting>

Program crashes after deleting a file on the local machine.

I run the latest version 3.4.0 of FileZilla client on Ubuntu 11.04. Before deleting a file on the local machine from inside the program, I had connected to an ftp server an copied a file across. After this, the program is frozen, and the only option to recover is to reboot the machine. The name of the deleted file was index.php~.

When changing the language from the default (which is Finnish on my computer) to English and then selecting File --> Exit, FileZilla FTP Client (v3.3.3) crashes. The crash doesn't occur if I don't change the language.

The error message is "Unhandled exception at 0x00a19e29 in filezilla.exe: 0xC0000005: Access violation reading location 0x002f004a."

using filezilla to download directories from a openVMS system. The OpenVMS system has a directory named "CON". filezilla creates a directory in windows called "CON" when I ftp the directory but it causes issue since this is an invalid directory name. Explorer wouldn't do anything when I tried to delete the 'CON' directory, cmd.exe gave an 'access is denied' when I would try to remove the directory. Checking security and trying to do anything on the folder that was created would just result in various errors about access denied, unexpected error, undetermined error etc. Researching I found that there certain keywords that are not allowed to be used as directory names and "CON" is one of those. I was able to eventually remove the directory but I had to search around to find a specific rd command to do this as the other options (rd, rmdir, explorer) wouldn't remove the directory.

FileZilla client 3.2.7.1 sends a client hello specifying support for TLS 1.1 only. This means that servers that only support TLS 1.0 cannot negotiate a connection.

Neither SSL 3.0 or TLS 1.0 is considered seriously insecure at this time, and they are much more widely deployed than TLS 1.1, so they should be supported.

Details:

From the TLS 1.1 RFC:

Appendix E. Backward Compatibility with SSL

For historical reasons and in order to avoid a profligate consumption of reserved port numbers, application protocols that are secured by TLS 1.1, TLS 1.0, SSL 3.0, and SSL 2.0 all frequently share the same connection port. For example, the https protocol (HTTP secured by SSL or TLS) uses port 443 regardless of which security protocol it is using. Thus, some mechanism must be determined to distinguish and negotiate among the various protocols.

TLS versions 1.1 and 1.0, and SSL 3.0 are very similar; thus, supporting both is easy. TLS clients who wish to negotiate with such older servers SHOULD send client hello messages using the SSL 3.0 record format and client hello structure, sending {3, 2} for the version field to note that they support TLS 1.1. If the server supports only TLS 1.0 or SSL 3.0, it will respond with a downrev 3.0 server hello; if it supports TLS 1.1 it will respond with a TLS 1.1 server hello. The negotiation then proceeds as appropriate for the negotiated protocol.

Similarly, a TLS 1.1 server that wishes to interoperate with TLS 1.0 or SSL 3.0 clients SHOULD accept SSL 3.0 client hello messages and respond with a SSL 3.0 server hello if an SSL 3.0 client hello with a version field of {3, 0} is received, denoting that this client does not support TLS. Similarly, if a SSL 3.0 or TLS 1.0 hello with a version field of {3, 1} is received, the server SHOULD respond with a TLS 1.0 hello with a version field of {3, 1}.

From a WireShark packet capture:

Frame 8 (126 bytes on wire, 126 bytes captured)

Ethernet II, Src: CompalIn_88:54:36 (00:1b:38:88:54:36), Dst: Cisco_fb:b8:00 (00:14:f1:fb:b8:00) Internet Protocol, Src: 10.20.69.248 (10.20.69.248), Dst: 10.20.239.21 (10.20.239.21) Transmission Control Protocol, Src Port: gsi (1850), Dst Port: 11932 (11932), Seq: 11, Ack: 81, Len: 72 Secure Socket Layer

SSL Record Layer: Handshake Protocol: Client Hello

Content Type: Handshake (22) Version: TLS 1.1 (0x0302) <-- This is the lowest version supported. Length: 67 Handshake Protocol: Client Hello

Handshake Type: Client Hello (1) Length: 63 Version: TLS 1.1 (0x0302) <-- And this is the preferred version. Random Session ID Length: 0 Cipher Suites Length: 24 Cipher Suites (12 suites) Compression Methods Length: 1 Compression Methods (1 method)

When under Remote Desktop session, attempt to bring FileZilla from the system tray will hang FileZilla.

When using SFTP and RADIUS/Securid authentication users are able to log in successfully. However, upon upload or download of files you are then prompted again to enter your next PASSCODE. Users should not be prompted fopr next passcode after successfully logging in to transfer files.

The problem occured after the update from 3.34.0. All later versions have problems with memory management, including most recent 3.40.0. The program keeps running in the background and can only be closed to start a new session after Ctrl-Alt-Del and ending the process manualy.

This behavior is always when an connection can not be made or when the transfer is interupted. After that is is not possible to open a new connection without closing the progrma and manualy ending the process in memory.

An other report mentions the same behavoir. That describes this while updating the version. That happens with me also.

FileZilla (newest versions) fails to connect to a VSFTPD server (2.1.2) using the standard timeout of 20 seconds in standard FTP mode on Windows XP machines. Clients never 'touch' the server as far as server logging is concerned and shows 'connection timed out could not connect to server'. Server is running RedHat Enterprise v5 patched as needed. Kernel: 2.6.18-92.1.22.el5 #1 SMP

1. Increasing the client side timeout to 30 seconds allows the clients to connect, but directory displays and other actions are sluggish.
2. This occurs on previously installed and used FileZilla clients, even those that have been uninstalled and reinstalled.
3. NEW/Fresh (never before installed) installs of FileZilla on Windows XP/Vista machines connect to the server quickly and flawlessly every time with the stock 20 second timeout.
4. We have turned OFF firewalls on the server side, no effect.
5. Disabled firewalls on Windows machines, no effect.
6. Using other FTP clients (cuteFTP, NCFTP, and command line clients) on the effected machines provides clean/quick FTP connections. Only FileZilla seems to have this problem.
7. This is occurring from various locations, and connection types so its not related to a particular network or location on the client side.
8. Problem can be reproduced every time.

After open FileZilla, it detects a new version (3.29.0 (2017-11-06)) but can't download it. Here is the installed version:

FileZilla Client

Version: 3.28.0

Build information:

Compiled for: x86_64-w64-mingw32 Compiled on: x86_64-pc-linux-gnu Build date: 2017-09-29 Compiled with: x86_64-w64-mingw32-gcc (GCC) 6.3.0 20170516 Compiler flags: -g -O2 -Wall

Linked against:

wxWidgets: 3.0.4 SQLite: 3.19.3 GnuTLS: 3.5.13

Operating system:

Name: Windows 7 (build 7601, Service Pack 1), 64-bit edition Version: 6.1 Platform: 64-bit system CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 Settings dir: C:\Users\Carlos Dias\AppData\Roaming\FileZilla\

In the quickconnectbar.xrc file:

• if the IP element is hidden (ID_QUICKCONNECT_HOST), there is no problem. The default IP or the IP specified in command line is well used.

• if the Port element is hidden (ID_QUICKCONNECT_PORT), the application craches! I need to hide the 2 elements and I don't understand why we don't have the same behavior. Is it possible to fix this problem please?

Thank you for your support.

FileZilla crash by clicking on "Enter directory" where the Folder name include UTF8 chars. Test Folder name: "test - 鬼脈轉生 帝輪十年經典"

Filezilla crashes when I access my laptop from FileZilla, then disconnect the laptop from my Homegroup and try to navigate away from the laptop directory.

Steps to reproduce the crash:

1. Connect a device to your homegroup
2. Access the device on FileZilla (Local site) by going to
   COMPUTERNAME
3. Disconnect the same device you access
4. Attempt to navigate away from the device

When I open FileZilla it crash. I just have a menu with FileZilla, no submenu and nothing else. I have to force him to leave.

This problem just started happening today. I cannot open the application on my Mac at work. As soon as I do, a Problem Report for FileZilla box pops up. Can someone please help me get this working again? It is essential to my web development work. Thanks.

FileZilla 3.45.1 was the only version I could start on my Mac, but now it crashes on launch. At the bottom of the message there is the report. All other newer versions, after installation, return the message "The application could not be opened"

Crash Report Process: filezilla [2641] Path: /Users/USER/Desktop/FileZilla.app/Contents/MacOS/filezilla Identifier: org.filezilla-project.filezilla Version: ??? Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: filezilla [2641] User ID: 501

Date/Time: 2020-01-30 09:59:52.787 +0100 OS Version: Mac OS X 10.14.6 (18G2022) Report Version: 12 Anonymous UUID: 01707240-4EEC-3652-E2D3-4CF3A5C4FA75

Time Awake Since Boot: 1200 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_CRASH (Code Signature Invalid) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace CODESIGNING, Code 0x1

kernel messages:

VM Regions Near 0 (cr2): -->

TEXT 0000000105cd8000-00000001067c9000 [ 10.9M] r-x/rwx SM=COW

Thread 0 Crashed: 0 0x000000010e54c000 _dyld_start + 0

Thread 0 crashed with X86 Thread State (64-bit):

rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000 rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007ffee9f27bc8

r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000

r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000 rip: 0x000000010e54c000 rfl: 0x0000000000000200 cr2: 0x0000000000000000

Logical CPU: 0 Error Code: 0x00000000 Trap Number: 0

Binary Images:

0x105cd8000 - 0x1067c8ff7 + (0) <2AA5D23A-5618-3011-9FE0-EB563ED44B45> 0x10e54b000 - 0x10e5b570f + (655.1.1) <B3D9DDCB-5AA7-3674-9608-16B5AA4AA494>

External Modification Summary:

Calls made by other processes targeting this process:

task_for_pid: 0 thread_create: 0 thread_set_state: 0

Calls made by this process:

task_for_pid: 0 thread_create: 0 thread_set_state: 0

Calls made by all processes on this machine:

task_for_pid: 489 thread_create: 0 thread_set_state: 0

VM Region Summary: ReadOnly portion of Libraries: Total=13.9M resident=0K(0%) swapped_out_or_unallocated=13.9M(100%) Writable regions: Total=8500K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8500K(100%)

VIRTUAL REGION

REGION TYPE SIZE COUNT (non-coalesced) =========== ======= ======= STACK GUARD 56.0M 1 Stack 8192K 1 DATA 1016K 4 LINKEDIT 2556K 2 TEXT 11.4M 2 shared memory 8K 2 =========== ======= ======= TOTAL 78.9M 12

Model: iMac18,3, BootROM 179.0.0.0.0, 4 processors, Intel Core i5, 3,8 GHz, 16 GB, SMC 2.41f1 Graphics: kHW_AMDRadeonPro580Item, Radeon Pro 580, spdisplays_pcie_device, 8 GB Memory Module: BANK 0/DIMM0, 8 GB, DDR4, 2400 MHz, 0x80AD, 0x484D413831475336414652384E2D554820202020 Memory Module: BANK 1/DIMM0, 8 GB, DDR4, 2400 MHz, 0x80AD, 0x484D413831475336414652384E2D554820202020 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x16F), Broadcom BCM43xx 1.0 (7.77.61.3 AirPortDriverBrcmNIC-1305.9) Bluetooth: Version 6.0.14d3, 3 services, 27 devices, 1 incoming serial ports Network Service: Ethernet, Ethernet, en0 Serial ATA Device: APPLE HDD ST3000DM001, 3 TB USB Device: USB 3.0 Bus USB Device: External USB 3.0 USB Device: My Book 1234 USB Device: M3 Portable USB Device: Bluetooth USB Host Controller USB Device: FaceTime HD Camera (Built-in) Thunderbolt Bus: iMac, Apple Inc., 41.1

FileZilla crashes every time I try to download something from a server to my computer.

A downloading FileZilla client crashes and loses the download queue on my friend's computer when I restart my computer which runs the FileZilla server application he is connected to. Last time the crash situation included an "Illegal operation" Windows error.

I have updated to 3.37.3 and after I have started a connection to a server, FileZilla chrashes. I have tried it with a fresh installation directory, but the same happens.

Last Loglines: 2018-10-03 20:38:52 31949 1 Befehl: AUTH TLS 2018-10-03 20:38:52 31949 1 Antwort: 234 AUTH TLS OK. 2018-10-03 20:38:52 31949 1 Status: Initialisiere TLS...

If I change back to 3.36.0, all is working normal.

Sincerely, Markus

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

Parameter[0]: 00000000 Parameter[1]: 00000004

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

I am using the latest of FileZilla 3.1.5.1. OS-Windows XP with SP3, RAM-2GB, Processor-Intel Core 2 Duo 1.80. I am uploading around 160000 jpg images to our site using FTP. I am using the anonymous account for the FTP. For the first time about 30000 images uploaded successfully. Suddenly the system restarted due to power fluctuation. I have again started uploading the same selecting the option "Overwrite is different size or source newer". But this time FileZilla crashed. I have again tried for 3 to 4 time but got the same. I have reinstalled FileZilla but the same problem occurs.

I am sending the windows error report along with snap shots