Opened 12 years ago

Last modified 12 years ago

#3164 closed Bug report

30 sec startup when disconnected network drives exists

Reported by: sire404 Owned by:
Priority: normal Component: Other
Keywords: Cc: sire404, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

FileZilla 3 beta 10 takes a very long time to start up if you have disconnected network drives in Windows.

Recreate problem:
tools / map network drive
choose another computer in the network

computer\c$ or whatever
save the connection with "reconnect at logon"
FileZilla still starts up fine
remove the other computer from the network (unplug network cable)
FileZilla now takes ~30 sec to start.

Related to [ 1578753 ] Scan Floppy and slow startup
http://sourceforge.net/tracker/index.php?func=detail&aid=1578753&group_id=21558&atid=887596

Change History (4)

comment:1 Changed 12 years ago by Tim Kosse

Won't fix. This is an issue only Microsoft can fix by changing their broken APIs.

comment:2 Changed 12 years ago by sire404

A workaround could be to NOT scan all drives at startup, only when chosen by the user?
I mean, scanning a CDROM or a network drive can be slow even when it's working.

comment:3 Changed 12 years ago by Tim Kosse

There is no scanning involved. Upon startup, FileZilla just calls the following two Windows API functions:
GetLogicalDriveStrings
GetVolumeInformation

And these functions blocking is clearly a design flaw in Windows, not a problem with FZ.

comment:4 Changed 12 years ago by sire404

This was fixed in 3.0.1 anyway. Thanks :)

Note: See TracTickets for help on using tickets.