Well it seems that I am back to the drawing board of sorts.
What I think I need to do is go back to basics and verify that EVERY
variable declared matches the final API call? Because no matter what I do,
I can NOT get the program to totally end...(I start out with about 2,485K at start (before enum)
and build up from there, and when done, I drop to 3,048 or so...but never totally release and
can not kill from Task Manager, nor SysInternals, but can die out if I reboot)
The other problem is that it is accumulative, each new copy can and will enum alllll the handles
from the previous copy (I have to rename each new copy to compile again obviously)
An odd side effect (which I think has inadvertently been solved since, was that
earlier tries would crash if the app lost focus, but by checking if the PID was
less or greater than 32767 and compensate, would get rid of the error, so I think
somewhere along the lines must have something to do with a LoByte Vs HiByte value in a DWORD?)
Now if I can just figure out what is holding the program in memory, then I KNOWWWWWwwwww I can get a
working concept running. Unfortunately I can not find a way to log errors, when the error is that there is
no error, just the idea someone hasn't replied yet (with and without threads)
------------------
What I think I need to do is go back to basics and verify that EVERY
variable declared matches the final API call? Because no matter what I do,
I can NOT get the program to totally end...(I start out with about 2,485K at start (before enum)
and build up from there, and when done, I drop to 3,048 or so...but never totally release and
can not kill from Task Manager, nor SysInternals, but can die out if I reboot)
The other problem is that it is accumulative, each new copy can and will enum alllll the handles
from the previous copy (I have to rename each new copy to compile again obviously)
An odd side effect (which I think has inadvertently been solved since, was that
earlier tries would crash if the app lost focus, but by checking if the PID was
less or greater than 32767 and compensate, would get rid of the error, so I think
somewhere along the lines must have something to do with a LoByte Vs HiByte value in a DWORD?)
Now if I can just figure out what is holding the program in memory, then I KNOWWWWWwwwww I can get a
working concept running. Unfortunately I can not find a way to log errors, when the error is that there is
no error, just the idea someone hasn't replied yet (with and without threads)
------------------
Comment