TC 9.0a CRASH TWinControl.WMSize loop detected

[thomasmolover]

---------------------------
Total Commander 9.0a
---------------------------
TWinControl.WMSize loop detected, the widgetset does not like the LCL bounds or sends unneeded wmsize messages: SmallBufferGroup:TMyGroupBox BoundsRealized=l=37,t=-9281,r=434,b=-9214 NewBoundsRealized=l=37,t=-29893697,r=434,b=-29893630.
TWinControl.WMSize loop detected, the widgetset does not like the LCL bounds or sends unneeded wmsize messages: SmallBufferGroup:TMyGroupBox BoundsRealized=l=37,t=-9281,r=434,b=-9214 NewBoundsRealized=l=37,t=-29893697,r=434,b=-29893630
Windows 10 10.0 (Build 15002), base: 0400000

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

Stack trace (x64):82196D
821629 40F2FD 829990 81E363 919381 907737 922883 824DE8
824F2B 82529D 825287 825287 825287 825287 81A780 8313C6

Press Ctrl+C to copy this report!
Continue execution?
---------------------------
是(Y) 否(N)
---------------------------

[Horst.Epp]

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

[thomasmolover]

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

I did NOT do any special what diffrence to my normal work

[Horst.Epp]

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

I did NOT do any special what diffrence to my normal work

Sorry but this is absolutely unsufficent for an analysis.
Why should the author know your normal work ?
When does the error occur ?
After starting TC ?
Start of a copy / move / delete / archive or what ?

[ts4242]

Sorry but this is absolutely unsufficent for an analysis.

Sometimes it is sufficient I have seen many reports like this one, the author can guess what was the user do from the stack trace, and he asks for more details if he need.

[ghisler(Author)]

The top and bottom coordinates (t and b) have extremely large negative values. Something must have moved TC far off screen. Any ideas?

[gdpr deleted 6]

(...) Any ideas?

Hm, is it perhaps related to this older bug report: -[8.51ß1] Error "TWinControl.WMSize loop detected" ?

Similarities between both bug reports aside, it is best if thomasmolover responds and explains about his system configuration and the situation in which the problem occurred (as already suggested by Horst).

[ghisler(Author)]

Yes, it's the same problem. Maybe some kind of multiple desktop software tried to move the window off screen?