We have an application running on a client that exhibits strange behavior. At random times during the day, the OK button (which calls the Form.Close method) on certain forms will not close the form. By this, I mean that the user clicks a button and displays in the trace that Form.Close has been called, but the form will not be closed.
The strange thing is that the form itself still responds, so they can click any button on the form, and the code behind the buttons will be executed, but the form simply will not be closed.
This condition lasts from a few seconds to several minutes. Then, suddenly, the form begins to move away and disappear. Really strange.
So, to repeat, the following will happen:
Form.ShowDialog() → Form displays- The user works with form buttons and clicks, etc.
Form.Close() called → User clicked the close button- A time passes when the form simply waits for closing, while still being responsive (during this time, a disappointed user several times forgot the close button without an answer).
- Suddenly the form is placed, and the result of the dialogue comes back from
Form.ShowDialog
Notes:
- I do not use threads like threading.
- At certain points in time, it is reported that the process
explorer.exestopped on the PC, can this affect the behavior of the form? We are planning a recreation of the PC.
My question is, does anyone know of a scenario that might trigger the behavior described above?
, , , Form.Close, , , Close, , .
, explorer.exe ?
.
***
, , .