xyplorer crashes unexpectedly

[admin]

Just tried it again. Demn! Not reproducible.

Neither here.

[Borut]

Hi! New RTE... The only "special" thing I can think of was that some logical drives in the network were not accessible at that time, due to unconnected servers. I probably started a script that closes all the tabs and it is possible that some of them were pointing to nonaccessible locations. So it was trying to access the impossible, or enumerating servers... (And it can also be that this RTE has nothing to do with these special circumstances). The worst of all: I was not in front of the screen as it happened. Presenting it here just for documentation purposes... I am quite sure that this can not be repeated and it is also of no importance.

Code: Select all

Error:  	10 (0x0000000A)
Desc:   	This array is fixed or temporarily locked
Dll:    	0
Proc:   	cLi@17

Source: 	XYplorer
XY ver: 	XYplorer 25.60.0100 - Lifetime License Enterprise
OS:     	Windows 7 Pro (Service Pack 1), 32-bit, Build 7601 (6.1)
Locale: 	3079 (de-AT)
ANSI:   	1252, ACP: 1252  (ANSI - Lateinisch I)
Font:   	Consolas 10,5, Tahoma 9, DBCS: No
DPI:    	96 (100%), 1920x1080

Date:   	2024-03-06 13:14:15

[admin]

It's not completely useless, I made a note of it.

[yuxt]

I just had a crash, which I assume is the same as what I previously met (but in this version there is error message as below). But again - it is only my guess that it is the same type of crash.

What I was doing is creating a new folder on a remote shared drive (and the folder is created successfully).

Hope the message helps:

Error: 9 (0x00000009)
Desc: Subscript out of range
Dll: 0
Proc: setCut@10
Count=66, CountAll=66, idxPos=12, Item=, CommonPath=

Source: XYplorer
XY ver: XYplorer 27.10.0300 - Lifetime License Enterprise
OS: Windows 10 Enterprise, 64-bit, Version 22H2, Build 19045.6093 (10.0)
Locale: 2052 (zh-CN)
ANSI: 936, ACP: 936 (ANSI/OEM - Simplified Chinese GBK)
Font: Microsoft YaHei UI 12.75, Noto Sans 11.25, DBCS: Yes
DPI: 96 (100%), 1920x1080

Date: 2025-08-04 16:09:59

[admin]

Interesting! Can you repeat the error when you do the same thing again?

PS: Whatever, it should be fixed in the next beta.

[yuxt]

Till now I cannot reproduce it. Will report once it happens