[reopened] RestoreMaxiTree with network drive kills performance
Re: [reopened] RestoreMaxiTree with network drive kills performance
Digging through the .ini, I found the tweak DisableSHChangeNotifyRegister and set it to 1.
I don't know if this means the tree can become inconsistent when other programs change the file/directory structure, but it stopped the freezing...
Edit: Weirdly enough, enabling DisableSHChangeNotifyRegister also made Configuration | General | Refresh, Icons, History | Auto-Refresh | Include network locations work as expected.
With DisableSHChangeNotifyRegister and Auto-Refresh | Include network locations enabled, XYplorer doesn't freeze. So far, things are looking good. But I have to use this set up for a little longer to see if there are any other (negative) side effects.
I don't know if this means the tree can become inconsistent when other programs change the file/directory structure, but it stopped the freezing...
Edit: Weirdly enough, enabling DisableSHChangeNotifyRegister also made Configuration | General | Refresh, Icons, History | Auto-Refresh | Include network locations work as expected.
With DisableSHChangeNotifyRegister and Auto-Refresh | Include network locations enabled, XYplorer doesn't freeze. So far, things are looking good. But I have to use this set up for a little longer to see if there are any other (negative) side effects.
-
- Site Admin
- Posts: 60544
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: [reopened] RestoreMaxiTree with network drive kills performance
1) Yes, it should make a difference. I'll look into this.daniel_m wrote: ↑17 Sep 2021 17:40 The most problematic setting seems to be
Configuration | General | Tree and List | Tree | Check existence of subfolders in tree | In network locations as well
in combination with
Configuration | General | Refresh, Icons, History | Auto-Refresh (disabling "Include network locations" doesn't make a difference, even though it should)
...
2) BTW, when it happens again in the current beta version you can have a look at the debug log (paste this into the address bar and press ENTER):
Code: Select all
dlog;
3)
F4
triggers a complete tree refresh. Make sure that nothing sends an F4 key to XYplorer.FAQ | XY News RSS | XY Twitter
Re: [reopened] RestoreMaxiTree with network drive kills performance
Great, I wasn't aware of beta versions with logging :-)
I collected 3 logs so far:
1) Double clicking a PDF in XYplorer
2) Double clicking a PDF in Windows File Explorer
3) Invoking the "Open with" file dialogue
All three show the exact same content. There are a lot of RF2 IN/OUT, all for the Tree.LoadMaxiTree entries on my NAS (but not the local HDDs). The time stamps confirm a 9 seconds freeze.
I will upload a log later this weekend, with directory entries cleaned up and linked to the Tree.LoadMaxiTree entries for easier reading and privacy.
And thanks a lot for looking into this. XYplorer comes with a quite heavy price tag. And yet, I didn't have to think twice buying 2 Pro licenses. I don't want to use this to pressure you into spending time on this issue. Instead I want to praise your making not only the best file explorer out there, but one that is so much better than anything else, I don't even consider using the second or third best file explorer. ... Which is a shame actually, as it keeps me from giving Linux a closer look
I collected 3 logs so far:
1) Double clicking a PDF in XYplorer
2) Double clicking a PDF in Windows File Explorer
3) Invoking the "Open with" file dialogue
All three show the exact same content. There are a lot of RF2 IN/OUT, all for the Tree.LoadMaxiTree entries on my NAS (but not the local HDDs). The time stamps confirm a 9 seconds freeze.
I will upload a log later this weekend, with directory entries cleaned up and linked to the Tree.LoadMaxiTree entries for easier reading and privacy.
And thanks a lot for looking into this. XYplorer comes with a quite heavy price tag. And yet, I didn't have to think twice buying 2 Pro licenses. I don't want to use this to pressure you into spending time on this issue. Instead I want to praise your making not only the best file explorer out there, but one that is so much better than anything else, I don't even consider using the second or third best file explorer. ... Which is a shame actually, as it keeps me from giving Linux a closer look
Re: [reopened] RestoreMaxiTree with network drive kills performance
Sorry, this took longer than expected
The log is best viewed in an editor like Notepad++ with "smart highlighting", that highlights all instances of marked text.
Also: Yes, it's all porn ... except for NAS:\G\G3\G31\G311\, which is my master's thesis.
The log is best viewed in an editor like Notepad++ with "smart highlighting", that highlights all instances of marked text.
- When I provoke XYplorer to freeze, the log always contains all entries from Tree.LoadMaxiTree that point to my NAS. Paths to local HDDs are absent.
- XYplorer seems to look for the existence (?) of the current path from the active tab, regardless of what that path is (e.g. Desktop, somewhere on the NAS, local HDDs).
- In all logs, only the first RF2 IN is Explicit:False, Exists:False. All other RF2 IN are Explicit:False, Exists:True.
Code: Select all
NAS = network drive
Current path (of active tab): NAS:\I\I2\I21\
XYplorer 22.20.0209 - Windows 10 Professional N, 64-bit, Release 2009, Build 19043.1237 - 2021-09-18 13:10:29.027
=====================================================================================================================
0 - 2021-09-18 12:36:02.296 --- Tree.LoadMaxiTree: <censored:-)>
38 entries pointing to local HDDs (none found anywhere later in the log)
39 entries pointing to NAS
NAS:\A\
NAS:\B\B12\
NAS:\B\B11\B111
NAS:\C\C2\
NAS:\C\C12\C123\
NAS:\C\C12\C122\
NAS:\C\C12\C121\C1212\
NAS:\C\C12\C121\C1211\C12111\C121111\ (missing RF2 IN/OUT of C121111)
NAS:\C\C11\C111\
NAS:\C\C1\
NAS:\D\D1\
NAS:\E\
NAS:\F\F2\
NAS:\F\F1\
NAS:\G\G3\G31\G311\
NAS:\G\G2\
NAS:\G\G1\G12\
NAS:\G\G1\G11\G111\
NAS:\H\H1\H11\H111\
NAS:\I\I2\I21\I211\ (missing RF2 IN/OUT of I211)
NAS:\I\I1\ (missing RF2 IN/OUT of I1)
NAS:\J\J2\
NAS:\J\J1\J15\
NAS:\J\J1\J14\
NAS:\J\J1\J13\J133\J1333\
NAS:\J\J1\J13\J133\J1332\
NAS:\J\J1\J13\J133\J1331\
NAS:\J\J1\J13\J132\J1324\
NAS:\J\J1\J13\J132\J1323\
NAS:\J\J1\J13\J132\J1322\
NAS:\J\J1\J13\J132\J1321\
NAS:\J\J1\J13\J131\
NAS:\J\J1\J12\
NAS:\J\J1\J11\J111\J1113\
NAS:\J\J1\J11\J111\J1112\
NAS:\J\J1\J11\J111\J1111\
NAS:\J\J1\J12\
NAS:\K\K1\K12\K121\K111\
NAS:\K\K1\K11\K111\
--------------------------------------------------------------------------------------------------
58.191 - 2021-09-18 12:37:00.487 --- RF2 IN: NAS:\, Explicit:False, Exists:False, Path:NAS:\I\I2\I21\
2 - 2021-09-18 12:37:00.489 --- RF2 IN: NAS:\A\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
53 - 2021-09-18 12:37:00.542 --- RF2 OUT: NAS:\A\
0 - 2021-09-18 12:37:00.542 --- RF2 IN: NAS:\B\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
264 - 2021-09-18 12:37:00.806 --- RF2 IN: NAS:\B\B12\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
38 - 2021-09-18 12:37:00.844 --- RF2 OUT: NAS:\B\B12\
1.333 - 2021-09-18 12:37:02.177 --- RF2 IN: NAS:\B\B11\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
38 - 2021-09-18 12:37:02.215 --- RF2 IN: NAS:\B\B11\B111, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
11 - 2021-09-18 12:37:02.226 --- RF2 OUT: NAS:\B\B11\B111
19 - 2021-09-18 12:37:02.245 --- RF2 OUT: NAS:\B\B11\
2 - 2021-09-18 12:37:02.247 --- RF2 OUT: NAS:\B\
6 - 2021-09-18 12:37:02.253 --- RF2 IN: NAS:\C\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
30 - 2021-09-18 12:37:02.283 --- RF2 IN: NAS:\C\C2\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
47 - 2021-09-18 12:37:02.330 --- RF2 OUT: NAS:\C\C2\
26 - 2021-09-18 12:37:02.356 --- RF2 IN: NAS:\C\C12\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
560 - 2021-09-18 12:37:02.916 --- RF2 IN: NAS:\C\C12\C123\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
70 - 2021-09-18 12:37:02.986 --- RF2 OUT: NAS:\C\C12\C123\
34 - 2021-09-18 12:37:03.020 --- RF2 IN: NAS:\C\C12\C122\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
56 - 2021-09-18 12:37:03.076 --- RF2 OUT: NAS:\C\C12\C122\
7 - 2021-09-18 12:37:03.083 --- RF2 IN: NAS:\C\C12\C121\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
77 - 2021-09-18 12:37:03.160 --- RF2 IN: NAS:\C\C12\C121\C1212\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
28 - 2021-09-18 12:37:03.188 --- RF2 OUT: NAS:\C\C12\C121\C1212\
7 - 2021-09-18 12:37:03.195 --- RF2 IN: NAS:\C\C12\C121\C1211\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
6 - 2021-09-18 12:37:03.201 --- RF2 IN: NAS:\C\C12\C121\C1211\C12111\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
444 - 2021-09-18 12:37:03.645 --- RF2 OUT: NAS:\C\C12\C121\C1211\C12111\
7 - 2021-09-18 12:37:03.652 --- RF2 OUT: NAS:\C\C12\C121\C1211\
9 - 2021-09-18 12:37:03.661 --- RF2 OUT: NAS:\C\C12\C121\
0 - 2021-09-18 12:37:03.661 --- RF2 OUT: NAS:\C\C12\
0 - 2021-09-18 12:37:03.661 --- RF2 IN: NAS:\C\C11\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
23 - 2021-09-18 12:37:03.684 --- RF2 IN: NAS:\C\C11\C111\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
98 - 2021-09-18 12:37:03.782 --- RF2 OUT: NAS:\C\C11\C111\
18 - 2021-09-18 12:37:03.800 --- RF2 OUT: NAS:\C\C11\
0 - 2021-09-18 12:37:03.800 --- RF2 IN: NAS:\C\C1\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
1.205 - 2021-09-18 12:37:05.005 --- RF2 OUT: NAS:\C\C1\
12 - 2021-09-18 12:37:05.017 --- RF2 OUT: NAS:\C\
22 - 2021-09-18 12:37:05.039 --- RF2 IN: NAS:\D\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
237 - 2021-09-18 12:37:05.276 --- RF2 IN: NAS:\D\D1\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
26 - 2021-09-18 12:37:05.302 --- RF2 OUT: NAS:\D\D1\
0 - 2021-09-18 12:37:05.302 --- RF2 OUT: NAS:\D\
4 - 2021-09-18 12:37:05.306 --- RF2 IN: NAS:\E\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
28 - 2021-09-18 12:37:05.334 --- RF2 OUT: NAS:\E\
2 - 2021-09-18 12:37:05.336 --- RF2 IN: NAS:\F\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
9 - 2021-09-18 12:37:05.345 --- RF2 IN: NAS:\F\F2\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
18 - 2021-09-18 12:37:05.363 --- RF2 OUT: NAS:\F\F2\
5 - 2021-09-18 12:37:05.368 --- RF2 IN: NAS:\F\F1\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
5 - 2021-09-18 12:37:05.373 --- RF2 OUT: NAS:\F\F1\
15 - 2021-09-18 12:37:05.388 --- RF2 OUT: NAS:\F\
1 - 2021-09-18 12:37:05.389 --- RF2 IN: NAS:\G\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
10 - 2021-09-18 12:37:05.400 --- RF2 IN: NAS:\G\G3\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
49 - 2021-09-18 12:37:05.449 --- RF2 IN: NAS:\G\G3\G31\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
39 - 2021-09-18 12:37:05.488 --- RF2 IN: NAS:\G\G3\G31\G311\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
18 - 2021-09-18 12:37:05.506 --- RF2 OUT: NAS:\G\G3\G31\G311\
3 - 2021-09-18 12:37:05.509 --- RF2 OUT: NAS:\G\G3\G31\
5 - 2021-09-18 12:37:05.514 --- RF2 OUT: NAS:\G\G3\
12 - 2021-09-18 12:37:05.526 --- RF2 IN: NAS:\G\G2\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
101 - 2021-09-18 12:37:05.627 --- RF2 OUT: NAS:\G\G2\
29 - 2021-09-18 12:37:05.656 --- RF2 IN: NAS:\G\G1\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
8 - 2021-09-18 12:37:05.664 --- RF2 IN: NAS:\G\G1\G12\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
110 - 2021-09-18 12:37:05.774 --- RF2 OUT: NAS:\G\G1\G12\
15 - 2021-09-18 12:37:05.789 --- RF2 IN: NAS:\G\G1\G11\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
10 - 2021-09-18 12:37:05.799 --- RF2 IN: NAS:\G\G1\G11\G111\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
376 - 2021-09-18 12:37:06.175 --- RF2 OUT: NAS:\G\G1\G11\G111\
23 - 2021-09-18 12:37:06.198 --- RF2 OUT: NAS:\G\G1\G11\
4 - 2021-09-18 12:37:06.202 --- RF2 OUT: NAS:\G\G1\
0 - 2021-09-18 12:37:06.202 --- RF2 OUT: NAS:\G\
2 - 2021-09-18 12:37:06.204 --- RF2 IN: NAS:\H\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
5 - 2021-09-18 12:37:06.209 --- RF2 IN: NAS:\H\H1\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
41 - 2021-09-18 12:37:06.250 --- RF2 IN: NAS:\H\H1\H11\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
5 - 2021-09-18 12:37:06.255 --- RF2 IN: NAS:\H\H1\H11\H111\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
88 - 2021-09-18 12:37:06.343 --- RF2 OUT: NAS:\H\H1\H11\H111\
5 - 2021-09-18 12:37:06.348 --- RF2 OUT: NAS:\H\H1\H11\
244 - 2021-09-18 12:37:06.592 --- RF2 OUT: NAS:\H\H1\
13 - 2021-09-18 12:37:06.605 --- RF2 OUT: NAS:\H\
7 - 2021-09-18 12:37:06.612 --- RF2 IN: NAS:\I\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
13 - 2021-09-18 12:37:06.625 --- RF2 IN: NAS:\I\I2\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
4 - 2021-09-18 12:37:06.629 --- RF2 IN: NAS:\I\I2\I21\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
41 - 2021-09-18 12:37:06.670 --- RF2 OUT: NAS:\I\I2\I21\
0 - 2021-09-18 12:37:06.670 --- RF2 OUT: NAS:\I\I2\
1.216 - 2021-09-18 12:37:07.886 --- RF2 OUT: NAS:\I\
2 - 2021-09-18 12:37:07.888 --- RF2 IN: NAS:\J\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
137 - 2021-09-18 12:37:08.025 --- RF2 IN: NAS:\J\J2\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
19 - 2021-09-18 12:37:08.044 --- RF2 OUT: NAS:\J\J2\
5 - 2021-09-18 12:37:08.049 --- RF2 IN: NAS:\J\J1\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
7 - 2021-09-18 12:37:08.056 --- RF2 IN: NAS:\J\J1\J15\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
12 - 2021-09-18 12:37:08.068 --- RF2 OUT: NAS:\J\J1\J15\
85 - 2021-09-18 12:37:08.153 --- RF2 IN: NAS:\J\J1\J14\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
55 - 2021-09-18 12:37:08.208 --- RF2 OUT: NAS:\J\J1\J14\
58 - 2021-09-18 12:37:08.266 --- RF2 IN: NAS:\J\J1\J13\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
31 - 2021-09-18 12:37:08.297 --- RF2 IN: NAS:\J\J1\J13\J133\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
21 - 2021-09-18 12:37:08.318 --- RF2 IN: NAS:\J\J1\J13\J133\J1333\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
12 - 2021-09-18 12:37:08.330 --- RF2 OUT: NAS:\J\J1\J13\J133\J1333\
0 - 2021-09-18 12:37:08.330 --- RF2 IN: NAS:\J\J1\J13\J133\J1332\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
24 - 2021-09-18 12:37:08.354 --- RF2 OUT: NAS:\J\J1\J13\J133\J1332\
9 - 2021-09-18 12:37:08.363 --- RF2 IN: NAS:\J\J1\J13\J133\J1331\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
39 - 2021-09-18 12:37:08.402 --- RF2 OUT: NAS:\J\J1\J13\J133\J1331\
13 - 2021-09-18 12:37:08.415 --- RF2 OUT: NAS:\J\J1\J13\J133\
8 - 2021-09-18 12:37:08.423 --- RF2 IN: NAS:\J\J1\J13\J132\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
23 - 2021-09-18 12:37:08.446 --- RF2 IN: NAS:\J\J1\J13\J132\J1324\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
19 - 2021-09-18 12:37:08.465 --- RF2 OUT: NAS:\J\J1\J13\J132\J1324\
0 - 2021-09-18 12:37:08.465 --- RF2 IN: NAS:\J\J1\J13\J132\J1323\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
21 - 2021-09-18 12:37:08.486 --- RF2 OUT: NAS:\J\J1\J13\J132\J1323\
0 - 2021-09-18 12:37:08.486 --- RF2 IN: NAS:\J\J1\J13\J132\J1322\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
23 - 2021-09-18 12:37:08.509 --- RF2 OUT: NAS:\J\J1\J13\J132\J1322\
49 - 2021-09-18 12:37:08.558 --- RF2 IN: NAS:\J\J1\J13\J132\J1321\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
24 - 2021-09-18 12:37:08.582 --- RF2 OUT: NAS:\J\J1\J13\J132\J1321\
0 - 2021-09-18 12:37:08.582 --- RF2 OUT: NAS:\J\J1\J13\J132\
31 - 2021-09-18 12:37:08.613 --- RF2 IN: NAS:\J\J1\J13\J131\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
73 - 2021-09-18 12:37:08.686 --- RF2 OUT: NAS:\J\J1\J13\J131\
36 - 2021-09-18 12:37:08.722 --- RF2 OUT: NAS:\J\J1\J13\
0 - 2021-09-18 12:37:08.722 --- RF2 IN: NAS:\J\J1\J12\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
83 - 2021-09-18 12:37:08.805 --- RF2 OUT: NAS:\J\J1\J12\
9 - 2021-09-18 12:37:08.814 --- RF2 IN: NAS:\J\J1\J11\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
51 - 2021-09-18 12:37:08.865 --- RF2 IN: NAS:\J\J1\J11\J111\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
5 - 2021-09-18 12:37:08.870 --- RF2 IN: NAS:\J\J1\J11\J111\J1113\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
61 - 2021-09-18 12:37:08.931 --- RF2 OUT: NAS:\J\J1\J11\J111\J1113\
0 - 2021-09-18 12:37:08.931 --- RF2 IN: NAS:\J\J1\J11\J111\J1112\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
117 - 2021-09-18 12:37:09.048 --- RF2 OUT: NAS:\J\J1\J11\J111\J1112\
14 - 2021-09-18 12:37:09.062 --- RF2 IN: NAS:\J\J1\J11\J111\J1111\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
26 - 2021-09-18 12:37:09.088 --- RF2 OUT: NAS:\J\J1\J11\J111\J1111\
0 - 2021-09-18 12:37:09.088 --- RF2 OUT: NAS:\J\J1\J11\J111\
0 - 2021-09-18 12:37:09.088 --- RF2 OUT: NAS:\J\J1\J11\
0 - 2021-09-18 12:37:09.088 --- RF2 IN: NAS:\J\J1\J12\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
68 - 2021-09-18 12:37:09.156 --- RF2 OUT: NAS:\J\J1\J12\
0 - 2021-09-18 12:37:09.156 --- RF2 OUT: NAS:\J\J1\
13 - 2021-09-18 12:37:09.169 --- RF2 OUT: NAS:\J\
35 - 2021-09-18 12:37:09.204 --- RF2 IN: NAS:\K\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
1 - 2021-09-18 12:37:09.205 --- RF2 IN: NAS:\K\K1\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
2 - 2021-09-18 12:37:09.207 --- RF2 IN: NAS:\K\K1\K12\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
4 - 2021-09-18 12:37:09.211 --- RF2 IN: NAS:\K\K1\K12\K121\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
2 - 2021-09-18 12:37:09.213 --- RF2 IN: NAS:\K\K1\K12\K121\K1211\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
11 - 2021-09-18 12:37:09.224 --- RF2 OUT: NAS:\K\K1\K12\K121\K1211\
0 - 2021-09-18 12:37:09.224 --- RF2 OUT: NAS:\K\K1\K12\K121\
0 - 2021-09-18 12:37:09.224 --- RF2 OUT: NAS:\K\K1\K12\
5 - 2021-09-18 12:37:09.229 --- RF2 IN: NAS:\K\K1\K11\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
3 - 2021-09-18 12:37:09.232 --- RF2 IN: NAS:\K\K1\K11\K111\, Explicit:False, Exists:True, Path:NAS:\I\I2\I21\
14 - 2021-09-18 12:37:09.246 --- RF2 OUT: NAS:\K\K1\K11\K111\
27 - 2021-09-18 12:37:09.273 --- RF2 OUT: NAS:\K\K1\K11\
0 - 2021-09-18 12:37:09.273 --- RF2 OUT: NAS:\K\K1\
0 - 2021-09-18 12:37:09.273 --- RF2 OUT: NAS:\K\
27 - 2021-09-18 12:37:09.300 --- RF2 OUT: NAS:\
-
- Site Admin
- Posts: 60544
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: [reopened] RestoreMaxiTree with network drive kills performance
Thanks, we're coming closer. At the end of the
Tree.LoadMaxiTree:
line are two Boolean values (True / False) which I would like to see (you censored them away)...FAQ | XY News RSS | XY Twitter
Re: [reopened] RestoreMaxiTree with network drive kills performance
Ah, sorry
They are both False.
They are both False.
-
- Site Admin
- Posts: 60544
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: [reopened] RestoreMaxiTree with network drive kills performance
OK, in the next beta (v22.20.0217) make sure to untick this: Configuration | General | Refresh, Icons, History | Auto-Refresh | Include network locations
It might make a difference to your case... I'm still not totally sure what's going on.
It might make a difference to your case... I'm still not totally sure what's going on.
FAQ | XY News RSS | XY Twitter
-
- Site Admin
- Posts: 60544
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: [reopened] RestoreMaxiTree with network drive kills performance
In v22.20.0218 I modified what's written to the debug log. I'd still like to know what exactly is causing the reload of the maxi tree...
FAQ | XY News RSS | XY Twitter
Re: [reopened] RestoreMaxiTree with network drive kills performance
Thanks a lot. I just tried 22.20.0218 with Auto-Refresh | Include network locations disabled ... and ... the RF2 IN/OUT are gone ... but ... the 10 seconds freeze is still there
There is nothing suspicious in the Windows Event Viewer. Gosh, I wish Windows had a logcat like Linux ...
As before, DisableSHChangeNotifyRegister=1 prevents freezes.
Code: Select all
0 - 2021-09-22 16:45:09.778 --- Tree.LoadMaxiTree: fReset=False, fEasyOnNetwork:=False <tree paths>
As before, DisableSHChangeNotifyRegister=1 prevents freezes.
-
- Site Admin
- Posts: 60544
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: [reopened] RestoreMaxiTree with network drive kills performance
There must be more in the debug log! Before the line you are showing.
FAQ | XY News RSS | XY Twitter
Re: [reopened] RestoreMaxiTree with network drive kills performance
I was surprised too. This was literally the only entry in the log.
Before that line, there was only version and system information
Here is a new log:
Before that line, there was only version and system information
Here is a new log:
Code: Select all
XYplorer 22.20.0218 - Windows 10 Professional N, 64-bit, Release 2009, Build 19043.1237 - 2021-09-22 19:00:21.510
=====================================================================================================================
0 - 2021-09-22 17:01:05.080 --- Tree.LoadMaxiTree: fReset=False, fEasyOnNetwork:=False <tree paths>
-
- Site Admin
- Posts: 60544
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: [reopened] RestoreMaxiTree with network drive kills performance
Then this must be the initial loading of the maxi tree right on startup. But the freeze we are talking about is not on startup, but later, right?
FAQ | XY News RSS | XY Twitter
Re: [reopened] RestoreMaxiTree with network drive kills performance
The start up with DisableSHChangeNotifyRegister enabled and disabled takes roughly the same time (~10-15 seconds). Once XYplorer is up and running, it stays unresponsive for a few seconds. The start up time doesn't seem excessive and it doesn't bother me. If this looks like the same freeze issue, it might be an additional clue...
And yes, the freezes happen after the start up. I provoked several freezes by opening documents and invoking the "Open with" dialogue. Besides the initial Tree.LoadMaxiTree, there is nothing else showing up in the log.
And yes, the freezes happen after the start up. I provoked several freezes by opening documents and invoking the "Open with" dialogue. Besides the initial Tree.LoadMaxiTree, there is nothing else showing up in the log.
-
- Site Admin
- Posts: 60544
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: [reopened] RestoreMaxiTree with network drive kills performance
The start up time should be improved by ticking Configuration | General | Startup & Exit | No network browsing on startup.
But your problem is freezing that happens later while using the app, right? And since "LoadMaxiTree" does not appear anymore in the debug log, it's clear that this has nothing to do with the freezing. We have to search elsewhere. I will upload another version (v22.20.0219) with new logging soon.
But your problem is freezing that happens later while using the app, right? And since "LoadMaxiTree" does not appear anymore in the debug log, it's clear that this has nothing to do with the freezing. We have to search elsewhere. I will upload another version (v22.20.0219) with new logging soon.
FAQ | XY News RSS | XY Twitter