After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 265658 - evolution-exchange-storage crashes often and randomly
evolution-exchange-storage crashes often and randomly
Status: RESOLVED INCOMPLETE
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
1.5
Other All
: Normal blocker
: 2.1
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2004-09-09 22:33 UTC by Raul Acevedo
Modified: 2004-09-11 01:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Raul Acevedo 2004-09-09 22:33:26 UTC 
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
Exchange-storage crashes all the time, at random times, for random reasons.
 Once it decides to crash, it will frequently crash for a while. 
Eventually, either through killing all evolution-related processes
(data-server, alarm-notify) and/or deleting the
exchange/ACCOUNT/personal/subfolders/Calendar/cache.ics file (which as bug#264403 is dealing with, tends to grow rather large at random times), it
will eventually calm down and things will be normal again.  But it does go
into crash mode frequently outside of what happens with cache.ics.

Unfortunately I can't reproduce this in any one scenario.... but it doesn't
take long.  In order to help, I'd like to know how to get a core dump or
stack trace or debugging output from connector so when this happens, I can
submit some useful information.  All I know is that exchange-storage is
extremely unstable, at random times for random reasons, and I'd really like
to do what I can to help you guys debug it.

I hate filing a non-specific bug report without a reproducible test case,
but this is happening so frequently that I figure I have to get the ball
rolling with something.  Thanks...
Comment 1 Raul Acevedo 2004-09-09 23:30:54 UTC 
BTW, I am having a LOT of problems with Connector 1.5.93.  Is there a
newer version out, closer to 2.0, that I can play with that might be
more stable?  I'd hate to waste everybody's time on bugs that have
been fixed.
Comment 2 Sarfraaz Ahmed 2004-09-10 05:29:46 UTC 
Yes, there is 1.5.94. To get a backtrace, attach gdb to the
evolution-exchange process when it crashes [ using gdb -p <process id>
]. then on the gdb prompt, type "thread apply all bt". Thats the
backtrace that would help us debug the crash.
Comment 3 Dan Winship 2004-09-10 13:58:29 UTC 
If you have bug-buddy installed, it should get run automatically
and can get you a stack trace and post it to bugzilla.

If not, you'd have to start evolution-exchange-storage under gdb,
and then when it crashes, type "thread apply all bt" and paste
all the output here
Comment 4 Raul Acevedo 2004-09-11 01:18:41 UTC 
I found a reproducible case, so I'm closing this.  See bug#265732.