On Thu, 2002-08-29 at 22:34, Shane R. Monroe wrote: > Sometimes... Out of nowhere ... The Bat just stops picking up mail. > Something INTERNAL hangs. NO visible issues - just a strange absence > of mail. Shut down THE BAT, and you get the message similar to "There > are still operations in progress. Want to exit when they are > finished?" Neither response allows you exit. Killing THE BAT task is > the only way out.
This may sound really silly, but I'm comming from a programmers point of view with this idea. It'd appear to me that an internal global variable is being set when you go to download your emails... then something may occur to terminate the connection prematurely, then that global variable (probably a boolean) is not reset to the state reporting that it is not doing anything. When this variable is set in a state reporting it is checking mails, all future mail checks are halted as TB! would still think you have a connection (a simple check to see if you have connections by variable instead of attempting to connect, and failing). Now the reason you cannot close TB! is because the OnClose event of the main application looks at this global boolean, and if it is set, it asks if you want to terminate the process, when you click Yes, it cannot find a process to terminate, so doesn't reset the boolean (which is wrong behaviour, but this is a theory)... so you are stuck in a loop. If you click no, it doesn't do anything again. > I was running 1.5x under the same conditions without the issue. IIRC, the 1.5x branch didn't have the active processes check for when you exited, instead if there was a running process, it wouldn't close, I don't think this was done via a global boolean of any type (from a theory stand point anyway), but more of a list of active processes. > Anyone else have a voice on this? Similar experiences? Possible > solutions? Maybe if somebody that has regular contact with the developers (Marck? Allie?) pose the above theory, they may have another stand point to view things from, and may take a look into what may be causing the global boolean not to be reset. Don't forget this is just a silly theory of mine, but I've ran into a similar problem in one of my applications, where it gets stuck in a loop, the first thing is it cannot open a file, but when it tries to close, it tries writing to that file it couldn't find, and causes an error, so you end up stuck. > I cannot recreate it ... and it doesn't happen very often. Maybe > once a month; twice at the most. Try seeing if you can terminate the connection in an abnormal way, such as 95% the way through picking up the last message, disconnect... *shrugs*... it may have the same effect, or TB! may know how to handle that event properly. -- Jonathan Angliss ([EMAIL PROTECTED]) ________________________________________________ Current version is 1.61 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
