Pages: 1
RSS
Bat takes foever to Exit
 
I am currently using version 3.99.3 and planning to upgrade to the latest release very soon. But I have been running in to a problem with the The Bat! taking an extraordinarily long time to exit.

While I do have it set to compress folders on exit, it has never taken this long (5 + minutes, sometimes). There are a few thousand emails in various folders, but this behavior did not occur when there was significantly more emails involved.

Also, the compress progress dialog has shown itself, run its progress, and it is long gone. We just see the hourglass for several minutes.

The task manager shows the bat using about 45-50% of the CPU during this period of several minutes.

It is running on a Vista Home Premium machine with a 3 gz Core Duo CPU and 2 gigs of RAM. No Antivirus or AntiSpam software is running.

Any ideas on why this might be happening?

Stefan
 
Bump?
 
I'll take a stab at this :oops:
With the Bat open, try running FOLDER / Maintenance Center. Make sure that "Check integrity" and "Repair" are checked (I have all 4 checked)

Just this time run it twice - the second time should be faster. Then close the bat and see if it closes faster. If it does, start going into folders and UNchecking "compress the folder" on all but your most active folders.
 
Rick,

Thanks much for the suggestions. Unfortunately, I have already run the check integrity and repair on all the folders. The weird thing is that process does not take extremely long, even the first time following a fair amount of activity.

I am used to the typical compress process, and it is not a big deal. If I manually execute it before closing, it does not seem to make a difference.

That is why I think The Bat! is somehow stuck doing something else (?!), but I cannot figure out what it is.
Like it is going into a coma for a while.... :(  
 
Some of the beta testers were having similar issues in earlier releases but I can't remember which ones  :oops:

The next step - you might consider upgrading. Your version 3 key will work in v4 until v4.1 is released.
 
Do you have ANY plugin installed in TB!? If so try disabling those. You wrote you don't have any Anti-Spma or Antivirus software running, I just want to make sure it is not caused by a plugin. Voyager had a terrible time exiting when I had Antisamsniper plugin installed.
 
It actually started with 3.9.99. I have not yet seen it happen with 4.0.14, but it is an intermittent thing - probably every once or twice a week.

When it does, I just go grab a cup of coffee (or beer) and hang out for a while. I am too afraid to cancel, as it might corrupt the database.
 
OK - just happened with 4.0.14 last night. Lasted 3-4 minutes. I just cannot figure out what The Bat is chewing on. Again, the folder compression (according to the progress dialog) is done and gone. So it appears to be bogging down on something esle.
 
I'm currently using the Pro version 4.0.28.1 and this and the previous version fails to remove thebat.exe from memory after closing the program.
To shutdown the computer I must force close this process, and if I've been running the computer for most of the day, there might be several instances of this application running.

I'm only running Win XP Pro.

Any ideas please, as I've run the file maintenance utility, but it makes no difference.

 
Anyone else having this issue of lengthy exit times?  

I'm using 4.0.24 currently, but I have been having this problem now since 3.x.  It may take The Bat! 10 - 15 minutes to shut down once the exit button is clicked.  I don't have it set to compress folders on exit, so I can't figure out what takes it so long to shutdown.

The exit delay seems to get longer the longer The Bat! has been up and running.  If I close it after only running The Bat! for a few hours, it will usually exit within a few seconds.  If The Bat! has been up for days, then it takes 10 minutes or longer.
 
Dale: Try minimizing it then closing it from a minimized state - that is almost instantaneous for me. (I always run the maintenance center before closing for the night ....)

I had slow closes a while back and someone told me to clean out the cache file. Someone else said that has nothing to do with it. Either way it won't hurt. It is located in your BAT mail folder and you should close the bat first.
(my path is "C:\Documents and Settings\Rick\Application Data\The Bat!\cache") find yours. I have 38 files after being open all day

I clean them out nightly with no ill effects

Rick
 
I've just noticed that the same thing is happening on one of my systems.  The Bat remains in the process list after exit, but it's using 0% CPU.

I've cleared the setting to compress folder on ALL folders and cleared the cached.  I've also upgraded to the latest version (4.0.24), but this is still happening.

It consistently happens on one system, but not on another.  So far, the only thing I can find that is different between the two is: the system where this happens has Avast installed, and The Bat is using the Avast plugin.  The system where things work fine is using Antivir and doesn't use any AV plugins.

I'll have to try removing the Avast plugin tonight to see if that fixes the problem system.
 
All right.  I've confirmed that on my system where The Bat was consistently not exiting, removing Avast from the "Virus Checking Plug-ins" options screen fixes the problem.

Actually, removing from the options dialog didn't work directly.  After I delete the plugin, pressing OK would cause The Bat to hang.  I had to manually rename the plugin to a different name, but that fixed it.

Stefan: I don't know if this solution would work for you.  I assume it's safe to remove the plugin, because most modern anti-virus programs can check any email program that uses standard POP3, IMAP or SMTP protocols.
 
Minimizing and then exiting has the beneficial effect of ridding the screen of The Bat! window, but it does not kill the underlying The Bat! process which continues to run.

Unlike Warner, my instance of The Bat! will use ~98% of the CPU as shown by task manager for quite a few minutes or until the process is manually killed.

I'm not using any plug-ins with The Bat!
Pages: 1