Loading lag when a dead mapped network drive exists

[Mesh]

I just tried out v16.00.0008 and found a bug loading XY.

If there is a dead mapped network drive (the target machine was turned off after it had been mapped to a drive letter), XY can take 15-30 seconds to load.

The last version I ran was 15.90.0031, and neither that nor any earlier version ever had this problem. All prior versions that I've tried always loaded instantly without fail, regardless of whether a dead mapped drive existed or not.

[admin]

Are you using a Locked tree?

[Mesh]

Are you using a Locked tree?

No. In fact, I've never used that function.

[admin]

Mini or Maxi Tree?

[admin]

Well, whatever, I cannot see anything suspicious.

If you get those long delays again, please run this line:

Code: Select all

text <get loadtimes>, 800, 680;

It will show where the time was spent.

[Mesh]

Here you go:

---

XY ver: XYplorer 16.00.0009
OS: Windows 7 Ultimate, 64-bit
Loaded: 2015-11-20 15:16:39 in 19,313 ms

0 ms: 114 ms - Start Load
114 ms: 19 ms - Init Language
133 ms: 17 ms - Load Language
150 ms: 11 ms - Load Settings
161 ms: 3 ms - Init Custom File Icons
164 ms: 12 ms - Init Controls
176 ms: 37 ms - Init Graphics
213 ms: 8 ms - Init Tabs
221 ms: 22 ms - Create Info Panel
243 ms: 36 ms - Set Interface Font
279 ms: 17 ms - Init Panes
296 ms: 20 ms - Init Tree
316 ms: 2 ms - Tab Icons
318 ms: 0 ms - Load Catalog
318 ms: 1 ms - Load Tags
319 ms: 5 ms - Load Maxi Tree
324 ms: 0 ms - Init Custom Toolbar Buttons
324 ms: 6 ms - Init UDC and KS
330 ms: 18,923 ms - Load This Pane
19,253 ms: 2 ms - Load Other Pane
19,255 ms: 25 ms - Layout Window
19,280 ms: 32 ms - Show Window
19,312 ms: 1 ms - Init Menus
19,313 ms: - Load Done

MaxiTree: Rows=14, Nodes=14, Expanded=1, Mapped Drives=2
Check Existence of Subfolders in Tree: Yes
Icon Overlays: Yes
Pane 1: Items=12/8, Pane 2: Items=0/0, Catalog: Items=8

[Mesh]

One of the default panes is the list of all drives (the one for the computer itself). I'm guessing that may be the issue, in which case, it's not a problem with XY so much as this particular pane causing a dead network drive to be polled (and the lag is due to the timeout waiting for it to load).

I don't see this normally because I never have any panes set to this. My panes are always set to existing path locations. This is probably the first time that I loaded a fresh version of XY while I had a dead mapped drive.

The lag, then, would be due to the OS and how it processes polling a dead network drive. So XY isn't doing anything wrong. The only question is whether or not XY should (and can) address this issue more gracefully than the OS itself. Otherwise, we can chalk this up to an OS issue and leave it be.

[admin]

Thanks, but...

The lag, then, would be due to the OS and how it processes polling a dead network drive. So XY isn't doing anything wrong. The only question is whether or not XY should (and can) address this issue more gracefully than the OS itself. Otherwise, we can chalk this up to an OS issue and leave it be.

I don't see why this should take so long. Did you check whether XY starts faster if you point the pane to another location?

[binocular222]

This is due to when open My Computer, Windows/XY tries to collect free/used space on all drives, thus causing a long delay when trying to read from dead network drive.

I experienced this issue daily and work around by:
- Map network drive when I am at work such as:

Code: Select all

Run "cmd /c net use H: ""\\VNPNHFSR02\KPMGgeneral"" /P:Yes"

- Unmap them when I return to home (thus no longer can access company's network drive:

Code: Select all

Run "cmd /c net use H: ""\\VNPNHFSR02\KPMGgeneral"" /Delete"

[admin]

I see.

Next version this setting will also skip polling the bytes in the drives listing:
Configuration | Startup & Exit | No network browsing on startup

[binocular222]

v16.00.0106: Start-up is instant now, but if I subsequently browse to My Computer, XY freeze again.
Solution maybe an option to disable querry network drives' size.

[admin]

Or test whether it's dead. The question is: How long does it take to determine the drive is dead?

Please try this script line (X is your dead mapped network drive):

Code: Select all

exist "X:\";

Is it fast?

[binocular222]

Test 1: Remotely connect to my company's network via VPN (slow wifi): Take about 2-3 secs

Code: Select all

Does "j:\" exist?

ExistFile: False
ExistPath: True
ExistFolder: True
ExistItemFF: False
ExistPathFF: True
ExistPathOrFile: True
ExistPathOrFileShell: True
ExistIcon: True
IsNetworkLocation: True
GetItemType: 3
Owner:

Test 2: Disconnect from my company's network: Take about 10 secs

Code: Select all

Does "j:\" exist?

ExistFile: False
ExistPath: False
ExistFolder: False
ExistItemFF: False
ExistPathFF: False
ExistPathOrFile: False
ExistPathOrFileShell: False
ExistIcon: True
IsNetworkLocation: True
GetItemType: 3
Owner:

[admin]

OK, thanks! I will try something in next beta...