Quote:
Originally Posted by pasita
+bump
See Zandry? ppl like this
p.s. figured I'd bring to your attention what's probably the most frustrating bug in TST: I basically have Permascan + AWL running constantly (set to permascan every 30 seconds or so)...but every once in a while, I'll notice that it hasn't popped up any new tables in a while, and then I'll glance in the bottom-right of the TST window and I'll see that the "Time: __" field says something like: 13,478s.
IOW,
TST sometimes HANGS indefinitely. It's really easy to boot it out of this indefinite hang, I just have to click the Cancel button, and then the Permascan + AWL cycles back to its regular 30s cycle.
So my Q's for you:
1) Were you aware of this 'hang'? (I've got to think that it affects all users who run Permascan+AWL frequently)
2) Do you know what causes it?
3) And may I be so bold as to suggest a very easy solution? Since the manual "fix" is to just click the CANCEL button, why don't you just insert some sort of logic that checks to see if the "Time: __" value is significantly greater than what the user has set as the PermaScan Interval? So for me, if I have PermaScan ON with an interval of 30 econds...if at any time the "Time: __" value is, say, 90 seconds, then it's clear evidence that TST is hanging and it should click Cancel"
Did that make sense?
EDIT
See this screenshot? See how the Time says 646s? That should NEVER happen (b/c I have Permascan interval set to 30s...when i see this, i know that TST is hanging indefinitely and I have to click CANCEL to get it to restart)
Last edited by teddyFBI; 10-11-2011 at 05:00 PM.