High Number Of Envirnoment Variables Crashes 64 Bit XYPlorer

[robertoleonardo]

XYPLORER VERSION: 28.30.1800 (but have been experiencing on beta builds for several months -- at least as far back as 28.30.0.1603)
WINDOWS VERSION: Win 11 26H2 build 26300.9032 (currently on dev build, but had same issue when on normal beta insider build on 25H1. I don't think it relates to the insider build and presumably would have the same issue on a non-insider build).
SCALING: 150%

I rely heavily on environment variables and have a bunch of them. A few months ago, 64 bit xyplorer stopped working for me on both of my machines. I've been using the 32-bit version (which continues to work fine) since then, but finally had some time to investigate the 64-bit issue this afternoon. The crashes appear to be because i crossed some threshold number of environment variables. The max number of variables 64 bit can handle seems to be somewhere around 256-260 or so. Unclear why the cutoff appears to be a bit fuzzy instead of an exact number, but probably not important.

fewer than 256-260 environment variables -- 64 bit works fine. more than that -- xyplorer 64 bit crashes immediately and silently at startup 100% of the time.

The process briefly appears in Task Manager, then exits without opening a window or showing an error. The trigger appears to be variable count, and not content. I reproduced it with meaningless dummy variables (`ZZTEST001=x`, etc.) -- the same cutoff applied somewhere around 256-260 variables.

Event Viewer:

Code: Select all

Faulting application name: XYplorer.exe, version: 28.30.0.1800
Faulting module name: ntdll.dll, version: 10.0.26100.9032
Exception code: 0xc0000374 (heap corruption)

[admin]

Good catch!

a) The 64-bit version (tB), as you observed, completely chokes at this. It's even worse: I cannot even start the app from the IDE, so no chance for me to do anything about it. It's totally in the hands of the tB team. I'll make a report.

b) The 32-bit version (VB6) runs but has an internal limit of 255 EVs, sorted alphabetically. The rest is simply ignored and won't be resolved. I can fix that.

[admin]

a) I could fix it!
b) I could fix it!

[robertoleonardo]

as always, you're the man - thank you!