Not noticing any with process explorer, but figured I'd ask anyway as it just seems like it should gobble up 100% of the cpu.
Okay here's the thing. I need to change one hash value if some different values change. So I tried making a 0 second timer that repeats forever thinking, since, it's time to run it again right after it executes, it's run up 100% of the cpu.
Here's the thing. It don't.
I'm not complaining as that simplifies my life dramatically
, but why? My guess is 0 doesn't actually mean 0.
Anyway anything I should watch out for using it as a means to monitor a hash value? I keep seeing this nightmare scenario where unforeseen things make the cpu usage shoots up to 100%
