Opened 15 years ago
Closed 15 years ago
#4695 closed Bug report (rejected)
Extended delay starting client
Reported by: | Rob | Owned by: | |
---|---|---|---|
Priority: | low | Component: | FileZilla Client |
Keywords: | Cc: | david.antila@… | |
Component version: | Operating system type: | Windows | |
Operating system version: | XP SP3 |
Description
There is an extended delay of around 1 to 2 minutes starting the client. Attaching a process monitor (logs attached) it can be seen that the process is trying to open the locale directory by traversing the hard drive. When the "locales" directory in c:\program files\filezilla is renamed to "locale" there is no delay.
FileZilla Client
Version: 3.2.6.1
Build information:
Compiled for: i586-pc-mingw32msvc
Compiled on: x86_64-unknown-linux-gnu
Build date: 2009-07-02
Compiled with: i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2)
Compiler flags: -g -O2 -Wall -g -fexceptions
Linked against:
wxWidgets: 2.8.10
GnuTLS: 2.8.1
Attachments (1)
Change History (4)
by , 15 years ago
Attachment: | Logfile.zip added |
---|
comment:1 by , 15 years ago
Resolution: | → rejected |
---|---|
Status: | new → closed |
There is something wrong with your system. Even if FileZilla would check a thousand directories, it wouldn't take longer than one second on a proper system.
Try formatting your disks, reinstalling Windows, FileZilla and nothing else. I'm certain it will start very fast then.
comment:2 by , 15 years ago
Cc: | added |
---|---|
Priority: | normal → critical |
Resolution: | rejected |
Status: | closed → reopened |
Hmmm...I experience the same problem (record is 3 min 16 sec to load) and the directory name change does nothing.
It is a bit unrealistic, don't you think, to ask the user to wipe their disk, reinstall Windows and install FileZilla?
Urge you to re-think this issue and perhaps provide a debug build so that those affected may test and give you some feedback. No doubt it is interaction-with-system related, but the recommended workaround is not workable in my view.
comment:3 by , 15 years ago
Priority: | critical → low |
---|---|
Resolution: | → rejected |
Status: | reopened → closed |
How is this critical? It's not a security vulnerability. It's low priority at best because it's an issue with your system only you can fix.
This is not a problem with FileZilla, your system is broken.
Try this: Format your disks, install Windows and FileZilla and nothing else. I can guarantee you a quick start.
Process Monitor Log Files