Crash

[MarkFilipak]

---------------------------
Total Commander 10.00
---------------------------
Out of memory.
Out of memory
Windows 10 Core 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):413C5A
4141E9 414333 412E7E AF0477 AF0CFD 6A7D1F 6CC9BF 8C1A60
8C1A11 40F60D 8AF3A0 8A3F53 99D251 8D71A0 995F60 7FF99A036D41

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

Pressing Ctrl+C worked, but it also provoked an audible alert.
Answering "No" had no consequence.
I had to Esc to quit the comparison at which point the comparison window closed and Total Commmander was nowhere to be found.
Windows must have closed Total Commander.

What provoked this issue:
After I began a comparison (41,672,379,209 bytes, each file) and there were differences, the "Compare contents" progress box closed and was replaced by a side-by-side window.
I rarely have seen that side-by-side window. In it, I noticed a drop down box:

Code: Select all

[16______][v] bytes

16 bytes? What does that mean?

Code: Select all

[_16______][v] bytes
|_8_______|
|_16______|
|_24______|
|_32______|

I changed the selection to '8' to see what would happen and immediately got the "Out of memory" notice above.

Update:
I'm replicating the issue. "Abort" doesn't work reliably.

Criticism:
Once the side-by-side window opens, there is no way to pause the comparison.
.
More Info: pagefile is 102GB.

[MarkFilipak]

Update (more info):
Monitoring via Winternals Process Explorer, it appears that when the comparison is abandoned, the memory is not released.

[ghisler(Author)]

Monitoring via Winternals Process Explorer, it appears that when the comparison is abandoned, the memory is not released.

Can you give me more details, please?
1. When did you abandon the comparison?
2. Was this after getting the out of memory error?

[MarkFilipak]

Hello Christian,

I can further replicate per your further guidance.

I was replicating the issue: Comparison of two, 2K Blu-ray videos (41,672,379,209 bytes, each file) with
32GB semiconductor memory
swapfile.sys 16,777,216 bytes
pagefile.sys 104,857,600,000 bytes

1. When did you abandon the comparison?

By "abandoned" I mean I quit the comparison via window "[X]" close button -- quiting via the comparison utiliity's [Abort] button or via "Esc" key are unreliable (or seem unreliable due to lack of visual confirmation).

Note that this does not cause the crash. The crash occured while binary comparison was in progress when I changed the "bytes" selection from '16' to '8' to see what would happen and immediately got the "Out of memory" notice. I did that to see what would happen because I did not know what '16' and '8', '24', '32' referred to and consequently I wanted to get Help but there is no way to pause the comparison in the side-by-side window. (Note that I now know that '8', '16', '24', '32' refer to hex display 'width' but the side-by-side window says just "bytes" with no clue that it means columns in the binary display window -- may I suggest that you modify "8 16 24 32 bytes" to "8 16 24 32 hexidecimal display columns"?)

2. Was this after getting the out of memory error?

No. Following the out of memory error I rebooted Windows and tried to replicate the actions that caused the crash. To further clarify, abandoning the comparision has nothing to do with the crash.

I await your further guidance.

Regards,
Mark Filipak.

[ghisler(Author)]

Thanks for the additional information, this will help me a lot analyzing the error.

[MarkFilipak]

You're welcome, Christian. Let me know if you want me to conduct tests or regressions.