I am having a problem tracking down a bug that when I close my program under certain conditions, it appears the program ends, but is still listed in the processes and is actually still running.
In my case if I am scanning the computer to open a certain serial port, and I close the program while its process of Open File, check if device attached, Close file that the process remains running.
So I figure thats the part of code to look at, but putting in a trace to write to a file shows nothing. and if I try the same under debug, and animate, then when I close, I do not see the ending process of steps....it just ends.
If I am done scanning, or found my port and then close, everything closes fine and the program is not listed in the processes anymore.
The only other places I can think to look is in my statusbar, or richedit routines because the scanning shows its status there, but not sure what to look for.
So some fundamental questions
Just some thoughts....but maybe someone can point out something I can do to track my closing, or something I do not know may be causing the problem? I am working on some code to demo the problem, but can not seem to replicate it yet
In my case if I am scanning the computer to open a certain serial port, and I close the program while its process of Open File, check if device attached, Close file that the process remains running.
So I figure thats the part of code to look at, but putting in a trace to write to a file shows nothing. and if I try the same under debug, and animate, then when I close, I do not see the ending process of steps....it just ends.
If I am done scanning, or found my port and then close, everything closes fine and the program is not listed in the processes anymore.
The only other places I can think to look is in my statusbar, or richedit routines because the scanning shows its status there, but not sure what to look for.
So some fundamental questions
- Could a file opened with Freefile, somehow not get closed? (but my ending routine, purposely closes it if open, so I don't think thats it
- Could Streamin somehow be not processing a message in its callback, and not passing it on and creating a endless loop that I am not aware of? (like a DefFrameProc not used would do to me?)
- Some similar thing with a statusbar?
- If a control or a dialog or a window that has been destroyed, and some routine try to do something with it cause a program to continue?
Just some thoughts....but maybe someone can point out something I can do to track my closing, or something I do not know may be causing the problem? I am working on some code to demo the problem, but can not seem to replicate it yet

Comment