Windows exception: C0000005 when changing from custom view back to all details view

[adoeller]

---------------------------
Total Commander 10.00ß8
---------------------------
Access violation at address 00401E19. Write of address 06A79E0C.
Access violation at address 00401E19. Write of address 06A79E0C
Windows 10 Professional 10.0 (Build 19042), base: 00400000

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

Windows exception: C0000005
Stack trace:
00401E19
004026AC 005C8210 005CBBE7 00502D78 004FDA3E 004693C3
0046978F 0044C90D 0044C843 0044ECC6 0044E912 >0042A392
0042A392 0044DEB0 0042A392 0042A392 0044DE06 0042A392
0044C90D 0044E912 0042A392 0044DEB0 0044DEB0 0042A392
0042FBCD 0042FC68
Raw:
00401DCC 00401E6D 004020AE 00402232 004026AC 004021D4
004023FB 00402D83 00402D91 004033D5 005C8CCB 004036BB
00419CA3 004D002C 00401DCC 00401E6D 0041833E 005C8210
00502D78 004FDA3E 0044EC6E 0044C90D 0044EBE1 0043B88B
00473CB6 0044DF7A 0044E912 0044E935 0042A392 00473CB6
0044DF7A 0044E912 0044DEB0 0042A392 0044539B 004454DA
0043BCBA 0044C90D 0044EBE1 0043B88B 00473CB6 0044DF7A
0044C843 0044ECC6 0044F189 0044C90D 0044EBE1 0044DF7A
0044E912 0044E935 0042A392 0044EBE1 0044DF7A 0044E912
0044DE06 0042A392 0044EC8B 0044F048 0047451A 0044DE06

Press Ctrl+C to copy this report!
Continue execution?
---------------------------
Ja Nein
---------------------------

i.e. changing from Image: https://www.dropbox.com/s/3r6yd22a4gj6hp4/TC_bug.jpg?raw=1 to Image: https://www.dropbox.com/s/jj17t7kg3kw5ahl/TC_bug2.jpg?raw=1

first the colums did not match the header row, and after a few seconds TC crashed.

[Horst.Epp]

Not confirmed here
May be some more details are necessary

[ghisler(Author)]

Please provide more information:
How did you switch from custom view to all details?

[adoeller]

I did a right click on the view row (name, ext., size, ...) and switched to the other view.
this may not be a reproduceable bug. if there is nothing in the stack trace to give you a hint, i will continue trying to find the reproduction steps.

Cheers,
Alex

[ghisler(Author)]

Yes, please do!

The stack trace only gives an indication that it was a problem with freeing memory which is no longer used, but not where and why.