Freezing

[Daniel0312]

Hi,
My setup : XY in on a network share and I start it from other computers on the network (actually VMware virtual machines).
A few days ago I found XY starting time was... much longer than it used to be. For more than 20 seconds it would completely freeze the system.
Once started, at times it would fail to save settings or even break the network enough that applications would 'lose' opened files.
This problem is the same on different 'clients' (win7 or win10).

So I set up a test install, on the same network share.

The first capture is from my usual XY.

WORK.png (27.87 KiB) Viewed 2452 times

The second is the fast-configured test one.

!TEST.png (34.71 KiB) Viewed 2452 times

I see no obvious difference in the settings and the times are very similar until "Go Start Path" (starting path being on a network share).
I did some more tests : if the starting path is local, XY starting time is ~2s OK for me, BUT the freeze still occurs, for ~20s, right after the XY window shows.

Has anybody got an idea ?
Thanks

[admin]

No idea. Probably some Windows hiccup. Do you still get it today?

[Daniel0312]

Unfortunately yes.
I've restarted every PC just in case but I get the same behavior .

[admin]

The first loadtimes log looks funny. All events are missing after Go Start Path : E:\Partage.... Probably there was some error while loading. Is there any error log in the app data folder?

[Daniel0312]

No error at all.
My interpretation of the missing events : windows freezes when reaching Go to Start Path on the network share and blocks the logging after that point. When the start path is local (no access to the network share...), the logging reaches the end.
But, it seems XY still needs to access the network share(s) after loading is done and I get the delay after.

[admin]

There is no way to block the logging. A mystery.

[Daniel0312]

Hum.... Windows is frozen, absolutely frozen.
In the case when the start path is local there is high cpu usage after XY loading, as if to catch up something.

[Daniel0312]

I did some more testing.
Working setup :

Code: Select all

E:\Partage\Install\!TEST\XYplorer
└── Data

Basic portable install.

Not working setup:

Code: Select all

E:\Partage\Mes Programmes\XYplorer
└── XYdata
    ├── !Icons
    ├── !Scripts
    ├── @Thumbnails
    ├── @Tools
    ├── 7!TEST
    ├── DANIEL-PC
    ├── SevenPro
    ├── USB
    └── Win10-Pro

Customized portable install :
Some folders common to every computer, a data folder per computer.

I made a copy of the working data folder to 7!TEST so all the profiles are equivalent : surprise, it doesn't work anymore !
I suppose it's the way my install is set up but it shouldn't make a difference.

[admin]

XYdata is the XYplorer app data folder? It contains Win10-Pro???

[Daniel0312]

Well... I guess I didn't explain enough, sorry about that.
XYdata contains the data folders of every computer.
From 7!TEST to W10-Pro, those are the profiles (data folders) for each computer I access though the network.
Typical folder structure :

Code: Select all

└── Win10-Pro
    ├── Catalogs
    ├── Columns
    ├── FindTemplates
    ├── Layouts
    ├── NewItems
    ├── Panes
    ├── Paper
    └── Temp

The name refers to the actual computer name so I can easily point to the wanted data folder.
I hope it clarifies things.

By the way, copying a non-working data folder to the other path made it work : it's definitely the structure.

[admin]

Can't you isolate the problem by changing the structure step by step?

[Daniel0312]

I'll give it a try... will report back, but it may take some time .
Thank you

[Daniel0312]

Got it ! And it had nothing to do with XY
The difference was in the shortcut I use(d) to start XY on every machine...
The network drive was mapped to a letter but the shortcut used the UNC name.
It seems that was the reason : as soon as I replaced the UNC name by the drive letter eveything was back to normal.
I really don't understand why this would matter or how this change has occured (I haven't touched that shorcut in ages). I'm in the process of migrating to win11 though...

Anyway, all is fine now.
Thank you for taking the time to have a look.