Ts2 Crashes On Crossfade Attempt Options

[takemon]

Summary:
TS2 crashes on crossfades.

Product Version and Format:
TS Version 2.2.3 and 96kHz, 24bit *.wav file

Description:
When I try to crossfade two regions, TS2 crashes unexpectedly with the following error:

Faulting application name: TS.exe, version: 2.2.3.0, time stamp: 0x62a1fe53
Faulting module name: TS.exe, version: 2.2.3.0, time stamp: 0x62a1fe53
Exception code: 0xc0000005
Fault offset: 0x0000000000292f9f
Faulting process id: 0x0x1FC4
Faulting application start time: 0x0x1D987C92CB707CA
Faulting application path: C:\Program Files\Ircam Lab TS\TS.exe
Faulting module path: C:\Program Files\Ircam Lab TS\TS.exe
Report Id: e3e82312-cefb-4ca4-b763-766ff95c01bf
Faulting package full name:
Faulting package-relative application ID:

Reproducibility:
- Always

System Information:
OS Name: Microsoft Windows 11 Pro
Version: 10.0.22621 Build 22621
System Type: x64-based PC
Processor: Intel® Core™ i7-9700F CPU @ 3.00GHz, 3000 Mhz, 8 Core(s), 8 Logical Processor(s)
Installed Physical Memory (RAM): 32.0 GB
Graphics Card: Nvidia GeForce GTX 1660 (8.0 Gbps)
Graphic Drivers Version: 531.79

[takemon]

Many thanks for your quick reply.
I uninstalled v2.2.3 and installed the version you provided.
When I unpack TS-install-2.2.4-dev.zip a folder called TS-install-2.2.4-dev is created. The folder contains a file named TS-install.exe (8.93 MB / 9,103,840 bytes). After the installation and when I start TS2 it still shows TS - 2.2.3 in the top left corner. The About TS information screen shows the same version. Are you sure you provided the correct version?

Regarding process monitor, please don't get me wrong. I've just loaded the sound file and switched to the Process Monitor. TS didn't try to create any temporary files. Instead it tries to read attributes (with success) from the Gong_Test_Preset_18-22_Mix.wav over and over again (forever). If you follow my instruction to reproduce the problem you will see what I mean. This behavior may be unrelated to the cross fade issue. I just wanted to mention it because it looks unusual. If you are unable to use Process Monitor, I can send you some screenshots if it helps.

Many thanks for looking into the issue!