Filezilla not opening up to previously used directory
Moderator: Project members
Filezilla not opening up to previously used directory
Current client: Version: 3.56.2
Operating system:
Name: Windows 10 (build 19043)
Version: 10.0
Platform: 32-bit system [virtual machine]
CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd
Settings dir: C:\Users\Mike Dean-V\AppData\Roaming\FileZilla\
Up until about a couple of months ago, the Filezilla client would open up to the last directory I had used to upload files
But since Oct. 19, when I last uploaded some golf html files, Filezilla would open up to that directory. Screenshot 2 shows the file I want to work from (but it doesn't remember that I had sorted it by last modified Screenshot 3 shows the sorted directory with files uploaded. Screenshot 4 shows me logging out of the server. At the point, I would expect Filezilla to open to the hockey directory on the local site ... But screenshot 5 opens back up to the golf directory (same as screenshot 1, but taken 3 minutes later) So I'm hoping that it's not something unique to the 32-bit Windows 10 (I have FileZilla on the 64-bit Windows 10 host, and it has been behaving well).
But if it is, would rolling back to a version before 3.56 get the local directory to behave properly?
Operating system:
Name: Windows 10 (build 19043)
Version: 10.0
Platform: 32-bit system [virtual machine]
CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd
Settings dir: C:\Users\Mike Dean-V\AppData\Roaming\FileZilla\
Up until about a couple of months ago, the Filezilla client would open up to the last directory I had used to upload files
But since Oct. 19, when I last uploaded some golf html files, Filezilla would open up to that directory. Screenshot 2 shows the file I want to work from (but it doesn't remember that I had sorted it by last modified Screenshot 3 shows the sorted directory with files uploaded. Screenshot 4 shows me logging out of the server. At the point, I would expect Filezilla to open to the hockey directory on the local site ... But screenshot 5 opens back up to the golf directory (same as screenshot 1, but taken 3 minutes later) So I'm hoping that it's not something unique to the 32-bit Windows 10 (I have FileZilla on the 64-bit Windows 10 host, and it has been behaving well).
But if it is, would rolling back to a version before 3.56 get the local directory to behave properly?
Re: Filezilla not opening up to previously used directory
After closing FileZilla, please use the Task Manager of Windows to check if the FileZilla process is really gone. A problem that I personally have with all 32bit FileZilla clients, for a fair while, is, that the process stays open when the window is closed. It will then not save settings correctly, and this may also be the reason the last directory isn't saved for you.
And yes, the problem is only in the 32bit clients, the 64bit ones close fine and save correctly.
A note: Even the 32bit processes will close and save correctly if you don't do any actions like connecting to servers, transfer files, etc. So, you might have success with opening FileZilla, setting the new local directory, and immediately close it again.
And yes, the problem is only in the 32bit clients, the 64bit ones close fine and save correctly.
A note: Even the 32bit processes will close and save correctly if you don't do any actions like connecting to servers, transfer files, etc. So, you might have success with opening FileZilla, setting the new local directory, and immediately close it again.
No support requests over PM! You will NOT get any reply!!!
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
Re: Filezilla not opening up to previously used directory
That is worth investigating (saved the response to a text file)
Meanwhile, I uploaded some files yesterday and today, so it remembered my previous settings
So, perhaps can put a knot in this thread
Meanwhile, I uploaded some files yesterday and today, so it remembered my previous settings
So, perhaps can put a knot in this thread
Re: Filezilla not opening up to previously used directory
I had gotten a suggestion to close the background process in Task Manager after I exit Filezilla.
I have faithfully done that, but in the past week or so, after uploading files from a tennis directory, I open Filezilla and it opens up in the hockey directory.
So something is going on behind the scenes that can't be fixed by the Task Manager step.
I have faithfully done that, but in the past week or so, after uploading files from a tennis directory, I open Filezilla and it opens up in the hockey directory.
So something is going on behind the scenes that can't be fixed by the Task Manager step.
Re: Filezilla not opening up to previously used directory
Task Manager close is forceful, it doesn't save settings. You could work around by defining Global Bookmarks for your most-used directories. Just use the Bookmarks menu, add a Global Bookmark, set the desired local (and maybe also the desired remote) directory. Rinse and repeat for the rest. Each time you call a Global Bookmark from that menu, FileZilla will automatically change the local (and the remote if defined and being connected) directory.
As for the last directory being saved, the chance is almost 100% if you open FileZilla, change the directory and close it right away. The issue with the stuck task only happens if you've done anything with it (connecting to servers, listing directories, doing transfers). I'm suspecting there is a thread from the connection/transfer department getting stuck.
As for the last directory being saved, the chance is almost 100% if you open FileZilla, change the directory and close it right away. The issue with the stuck task only happens if you've done anything with it (connecting to servers, listing directories, doing transfers). I'm suspecting there is a thread from the connection/transfer department getting stuck.
No support requests over PM! You will NOT get any reply!!!
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
Re: Filezilla not opening up to previously used directory
Well, the switching to the desired directory, closing and restarting FileZilla worked. Thanks.
Re: Filezilla not opening up to previously used directory
A dump would bring clarity.As for the last directory being saved, the chance is almost 100% if you open FileZilla, change the directory and close it right away. The issue with the stuck task only happens if you've done anything with it (connecting to servers, listing directories, doing transfers). I'm suspecting there is a thread from the connection/transfer department getting stuck.
Re: Filezilla not opening up to previously used directory
Are the steps for producing and posting a dump somewhere on this board?
Re: Filezilla not opening up to previously used directory
Usually, when you have a hanging process in Task Manager (Details tab), you can right-click it and select "Create dump file".
No support requests over PM! You will NOT get any reply!!!
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
Re: Filezilla not opening up to previously used directory
That creates a full dump which tends to be gigantic and contains sensitive information like passwords. A minidump is more than sufficient and it tends to not contain sensitive information, you can create it with Process Explorer.
Re: Filezilla not opening up to previously used directory
@botg Wouldn't it help to provide debugging symbols, at least for some versions?
No support requests over PM! You will NOT get any reply!!!
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
Re: Filezilla not opening up to previously used directory
OK...since I'm using FileZilla on a Windows 10 32-bit machine, I will see what that dump file will do.
Meanwhile, using a Microsoft debugging tool, I got the following:
---------
So, I have no idea what to look for....
Meanwhile, using a Microsoft debugging tool, I got the following:
Code: Select all
Microsoft (R) Windows Debugger Version 10.0.22549.1000 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\00000-shared\filezilla.DMP]
User Mini Dump File with Full Memory: Only application data is available
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 19043 UP Free x86 compatible
Product: WinNt, suite: SingleUserTS
Edition build lab: 19041.1.x86fre.vb_release.191206-1406
Machine Name:
Debug session time: Mon Mar 7 16:12:34.000 2022 (UTC - 7:00)
System Uptime: 0 days 0:27:42.409
Process Uptime: 0 days 0:03:02.000
................................................................
...............................................
Loading unloaded module list
....
For analysis of this file, run !analyze -v
eax=0000000b ebx=011d9c8c ecx=00baf360 edx=773d2750 esi=00000000 edi=00000298
eip=773d2750 esp=00baf360 ebp=00baf3d4 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200246
ntdll!KiFastSystemCallRet:
773d2750 c3 ret
Microsoft (R) Windows Debugger Version 10.0.22549.1000 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\00000-shared\filezilla.DMP]
User Mini Dump File with Full Memory: Only application data is available
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 19043 UP Free x86 compatible
Product: WinNt, suite: SingleUserTS
Edition build lab: 19041.1.x86fre.vb_release.191206-1406
Machine Name:
Debug session time: Mon Mar 7 16:12:34.000 2022 (UTC - 7:00)
System Uptime: 0 days 0:27:42.409
Process Uptime: 0 days 0:03:02.000
................................................................
...............................................
Loading unloaded module list
....
For analysis of this file, run !analyze -v
eax=0000000b ebx=011d9c8c ecx=00baf360 edx=773d2750 esi=00000000 edi=00000298
eip=773d2750 esp=00baf360 ebp=00baf3d4 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200246
ntdll!KiFastSystemCallRet:
773d2750 c3 ret
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
*** WARNING: Unable to verify timestamp for libstdc++-6.dll
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2921
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 25956
Key : Analysis.Init.CPU.mSec
Value: 1296
Key : Analysis.Init.Elapsed.mSec
Value: 51066
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
Key : Timeline.OS.Boot.DeltaSec
Value: 1662
Key : Timeline.Process.Start.DeltaSec
Value: 182
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
Key : WER.Process.Version
Value: 3.57.0.0
FILE_IN_CAB: filezilla.DMP
NTGLOBALFLAG: 0
PROCESS_BAM_CURRENT_THROTTLED: 0
PROCESS_BAM_PREVIOUS_THROTTLED: 0
APPLICATION_VERIFIER_FLAGS: 0
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0
FAULTING_THREAD: 00001dbc
PROCESS_NAME: filezilla.exe
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_CODE_STR: 80000003
STACK_TEXT:
00baf35c 773ce7da 754dd2b0 00000298 00000000 ntdll!KiFastSystemCallRet
00baf360 754dd2b0 00000298 00000000 00000000 ntdll!NtWaitForSingleObject+0xa
00baf3d4 754dd1f2 00000298 ffffffff 00000000 KERNELBASE!WaitForSingleObjectEx+0xb0
00baf3e8 5571e131 00000298 ffffffff 00baf84c KERNELBASE!WaitForSingleObject+0x12
WARNING: Stack unwind information not available. Following frames may be wrong.
00baf408 556e28e6 011d99c8 00000038 012082b8 libfilezilla_23!ZN2fz6thread4joinEv+0x21
00baf418 5570e48c 046bc5e8 012082d4 012082bc libfilezilla_23!ZN2fz11thread_poolD1Ev+0xb6
00baf458 7b76684f 00baf488 01208468 00000003 libfilezilla_23!ZN2fz5mutexD2Ev+0xc
00baf468 7b9731c6 01208c54 fffffffe 045faf58 libfzclient_private_3_57_0!ZN23CFileZillaEngineContextD1Ev+0x28f
00baf478 7b981c93 011effd0 0000001c 7b6f8090 wxbase30u_gcc_custom!ZN12wxEvtHandlerD1Ev+0x136
00baf4a8 005f951c 01247510 000001a8 00000000 wxbase30u_gcc_custom!ZN14wxMSWTimerImpl5StartEib+0x593
00baf4cc 75d87379 00420000 0064b030 01208c0c filezilla!WinMain+0x1be4c
00baf4f8 005f922b 00baf4e0 00000000 00baf84c msvcrt!free+0x69
00baf588 7a1bc4cf 00baf5b4 00baf6d0 00baf708 filezilla!WinMain+0x1bb5b
00baf5e8 7b9a0fa4 00000020 00baf6d8 00baf708 wxmsw30u_core_gcc_custom!ZN9wxAppBase11ProcessIdleEv+0xf
00baf708 005dd6f8 005d0000 00000000 00000000 wxbase30u_gcc_custom!ZN17wxEventLoopManual5DoRunEv+0xd4
00baf748 005d1396 00000034 011da16c 00426b34 filezilla!WinMain+0x28
00baf7e8 7724cfc9 00000000 7724cfc9 0025f000 filezilla+0x1396
00baf800 773626c5 0025f000 98f1815e 00000000 kernel32!BaseThreadInitThunk+0x19
00baf85c 77362699 ffffffff 773e5c9f 00000000 ntdll!__RtlUserThreadStart+0x2b
00baf86c 00000000 005d14b0 0025f000 00000000 ntdll!_RtlUserThreadStart+0x1b
STACK_COMMAND: ~0s; .ecxr ; kb
SYMBOL_NAME: libfilezilla_23+21
MODULE_NAME: libfilezilla_23
IMAGE_NAME: libfilezilla-23.dll
FAILURE_BUCKET_ID: BREAKPOINT_80000003_libfilezilla-23.dll!Unknown
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x86
OSNAME: Windows 10
IMAGE_VERSION: 0.35.0.0
FAILURE_ID_HASH: {1ab65e97-b2d8-d4e8-6200-9c220209d6b1}
Followup: MachineOwner
So, I have no idea what to look for....
Last edited by boco on 2022-03-08 00:36, edited 1 time in total.
Reason: Sanitized the debug output with code tags.
Reason: Sanitized the debug output with code tags.
Re: Filezilla not opening up to previously used directory
Have a look at the stacks of the other threads in the process.