Something else I thought of is the ini file. Because there is an ini file read when opening the window in order to get the window state and position and at some point a file write back to the ini probably when the window is closed, I also wonder if its a disk read/write issue
Have you tried disabling the ini file window positions so its not using it to get the window position?
I’m not against the use of a logging file of sorts because like using debugview, the last entry written to file or sent to debugview will be around where it hangs, but if its something in the clarion runtime, writing to file which uses the clarion runtime could make it harder to isolate.
@vitesse mentioned using string theory to do the log writing here OutputDebugString directly to file? - #17 by vitesse.
If stringtheory is using windows api’s and not the clarion runtime to read/write to files, this could also work at helping to isolate the clarion runtime instead of using debugview, but if its a windows disk writing issue because there is a lot going on here in a very very short space of time, would writing to disk help instead of sending it to debugview where it sits in memory until saved to disk?
So can you add some logging to the abc classes then to get more info?