Stack trace (x64):8C2F9E -- Range check error.

[kkimber]

---------------------------
Total Commander 9.20ß1
---------------------------
Range check error.
Range check error
Windows 10 Enterprise 10.0 (Build 17134), base: 0400000

Please report this error to the Author, with a description
of what you were doing when this error occurred!

Stack trace (x64):8C2F9E

Press Ctrl+C to copy this report!
Continue execution?
---------------------------
Yes No
---------------------------

[Stefan2]

...

, with a description of what you were doing when this error occurred!

...

 

[tuska]

According to an email from Mr. Ghisler, the problem "Range Check Error" will be fixed in Beta 2.
See also: viewtopic.php?p=340665&sid=43fcdb68b4f293a24265cf7527c6dd71#340665

[ghisler(Author)]

This should be fixed in TC 9.20 beta 2, please test it!

[deus-ex]

Like tuska referred to this thread, the condition that triggered the "Range Check Error" for me was fixed with 9.20ß2.

However, since using 9.20ß2 I experienced the "Range Check Error" again under different conditions, as I described in the mentioned thread. Unfortunately I was not able to reproduce the error which makes it quite difficult to fix.

There is another condition related to RAR multipart-archives that can trigger a "Range Check Error", reported here.

[ghisler(Author)]

I don't think that they are directly related. So far I couldn't reproduce either of these two.

[ghisler(Author)]

OK, I finally found out what is causing this! I switched from Windows 7 to 10 - not as an update, but as a parallel installation. When doing this, some settings of the Lazarus/FPC compiler were lost, and the library (but not Total Commander itself) was suddenly compiled with range checking on. Turning that off seems to fix all remaining range check errors.

[ghisler(Author)]

This should finally be fixed in beta 3, please test it!

[deus-ex]

After using beta 3 regularly since two days I can confirm that the issues I reported in this thread appear to be finally fixed. Thanks, Christian.