evolution assert failure: *** glibc detected *** evolution: free(): invalid pointer: 0x00007f6c7841e2c0 ***

[iMac]

Just sending an email. Upon re-send, after recovery following restart it sent fine so it appeared to be unrelated to content. Similar named reports (693583, 475113) seemed outdated, so I've re-filed this one.

I obfuscated the obvious email in the StacktraceTop below.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: evolution 3.2.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.0.0-15.25-generic 3.0.13
Uname: Linux 3.0.0-15-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
AssertionMessage: *** glibc detected *** evolution: free(): invalid pointer: 0x00007f6c7841e2c0 ***
CrashCounter: 1
Date: Mon Jan 9 11:05:32 2012
ExecutablePath: /usr/bin/evolution
ProcCmdline: evolution
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
Signal: 6
SourcePackage: evolution
StacktraceTop:
 __libc_message (do_abort=2, fmt=0x7f6c76cbb0d8 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=3, str=0x7f6c76cb80ef "free(): invalid pointer", ptr=<optimized out>) at malloc.c:6283
 __GI___libc_free (mem=<optimized out>) at malloc.c:3738
 bbdb_do_it (email=0x7f6c7bd11910 "<email address hidden>", name=<optimized out>, client=0x7f6c7bc4fca0) at bbdb.c:403
 bbdb_do_in_thread (data=0x7f6c7bc4fca0) at bbdb.c:220
Title: evolution assert failure: *** glibc detected *** evolution: free(): invalid pointer: 0x00007f6c7841e2c0 ***
UpgradeStatus: Upgraded to oneiric on 2011-10-28 (72 days ago)
UserGroups: adm admin cdrom dialout dip disk fax fuse libvirtd lpadmin mythtv netdev plugdev pulse pulse-access sambashare scanner tape vboxusers vde2-net video

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #693583, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.