evolution-exchange-storage crashed with signal 5 in g_malloc()

[Wilbur Harvey]

Binary package hint: evolution-exchange

Exchange is crashing VERY often. Mostly it seems to be accessing messages.
It continually says that it lost connection to the backend process.
Unfortunately I have to use evolution here at work to connect to our windows mail system.
It REALLY sucks. This crashing has been going on for some time.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sat Feb 23 10:06:44 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/evolution/2.22/evolution-exchange-storage
NonfreeKernelModules: vmnet vmmon nvidia
Package: evolution-exchange 2.21.91-0ubuntu2
PackageArchitecture: amd64
ProcCmdline: /usr/lib/evolution/2.22/evolution-exchange-storage --oaf-activate-iid=OAFIID:GNOME_Evolution_Exchange_Component_Factory:2.22 --oaf-ior-fd=35
ProcCwd: /
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 SHELL=/bin/bash
Signal: 5
SourcePackage: evolution-exchange
StacktraceTop:
 g_malloc () from /usr/lib/libglib-2.0.so.0
 g_strndup () from /usr/lib/libglib-2.0.so.0
 ?? ()
 ?? ()
 g_main_context_dispatch ()
Title: evolution-exchange-storage crashed with signal 5 in g_malloc()
Uname: Linux hplws4 2.6.24-8-generic #1 SMP Thu Feb 14 20:13:27 UTC 2008 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lp lpadmin plugdev powerdev sambashare scanner video

[Apport retracing service (apport)]

StacktraceTop:IA__g_malloc (n_bytes=6739990885104091065) at /build/buildd/glib2.0-2.15.5/glib/gmem.c:135
IA__g_strndup (str=0x7ebc1dd7401e883 <Address 0x7ebc1dd7401e883 out of bounds>, n=6739990885104091064)
get_message (stub=0x6d56b0, folder_name=0xd91f00 "personal/Inbox", uid=<value optimized out>)
connection_handler (source=<value optimized out>, condition=<value optimized out>, data=0x6d56b0)
IA__g_main_context_dispatch (context=0x687100) at /build/buildd/glib2.0-2.15.5/glib/gmain.c:2064

[Wilbur Harvey (wilbur-harvey-spirentcom)]

Still happening even though I now have the correct global catalog server.

[Sebastien Bacher (seb128)]

the stacktrace seems similar to bug #236781 which has been fixed to hardy-updates now

[Paul Smith (psmith-gnu)]

I agree; the stacktrace shows status = 404 in get_message, which is the smoking gun for this bug.