Re: [Evolution] evolution taking 5+ minutes to shut down

[Not Zed <notzed ximian com>]

I suggest filing a bug (bugzilla.ximian.com), well, after trying the
suggestion at the end of this text.

Curious, does X totally lock up, or just run like a pig?

Other info that will help (if you dont supply it we'll ask anyway :)

 - the CAMEL_VERBOSE_DEBUG=1 log as suggested by Ettore (run
"CAMEL_VERBISE_DEBUG=1 evolution-1.3" in a terminal)
 - run evolution-1.3 in gdb.  Do some stuff, and quit so that things
start going haywire.  ctrl-c in gdb (if you can't ... that could be a
problem, try running it from a virtual console perhaps), and run 'thread
apply all bt' - this will show what code is running.

syncing maildir folders should be almost instantaneous, so something's
getting screwed.  my guess is its the dreaded indexer-goes-nuts bug.  it
generates massive temporary files that then shrink back to normal size -
if it doesn't fill up the disk first.  could try rm'ing any *.ibex*
files in your folders, and restart.

On Wed, 2003-06-11 at 22:17, Jason 'vanRijn' Kasper wrote:
> As a prelude, I am running evo 1.3.92 on debian sid, on a P4 1.8G laptop
> with 1G of RAM.  I keep all of my mail in Maildir format in ~/Maildir,
> which takes up 86M, and evolution of course has its own directory in
> ~/evolution, which takes up 18M.  All of my filesystems are
> XFS--recently upgraded to kernel-space 1.2.  All your base are... no,
> nevermind.
>
> I typically suspend my laptop at the end of the work day and resume it
> at home, then suspend and repeat the next day, etc.  Thus, I typically
> leave eveolution running for days and days at a time.  
>
> As of late, I've been noticing that evolution takes a REALLY long time
> to shut down, and while it does so, X locks up until it is done.  I
> notice that my hard drive is spinning constantly and at gkrellm's last
> update, it shows my hda traffic at 2.6M/s+.  
>
> I just rebooted yesterday for a new kernel and restarted evolution, then
> suspended at end of day,  resumed last night, and closed evolution this
> morning (note: evolution was running for less than 24 hours this time). 
> It took 7 minutes between when evolution popped up it's "evolution is
> closing" dialog window and when I finally was allowed to use my computer
> again.
>
> My questions: 
>
> - what in blazes is evolution doing between when it pops up its
> "evolution is closing" window and when it's done?
>
> - what in my described-above system could be contributing to this 7
> minutes that I get to sit quietly and wait for the "now closing" window
> to go away?
>
> - is anyone else seeing this???
>
> - even though I've started evo with "nice evolution", my system locks
> completely and I'm unable to even switch to a VC.  Is there any way I
> can debug this thing??
>
> TIA.