evolution crashed with SIGSEGV in g_datalist_id_set_data_full()

[dieterv]

Binary package hint: evolution

Running updated jaunty beta.
Crash in evolution happens when i was moving between messages using the keyboard and evolution was checking for new mail.

ProblemType: Crash
Architecture: i386
Disassembly: 0x0:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/evolution
NonfreeKernelModules: nvidia
Package: evolution 2.26.0-0ubuntu3
ProcCmdline: evolution --component=mail
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_datalist_id_set_data_full ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: evolution crashed with SIGSEGV in g_datalist_id_set_data_full()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[dieterv (dieterv77)]

Just another comment, i'm using evolution to connect to an imap server, all messages are kept on the server.

it seems quite easy to reproduce this bug for me.
I just open evolution, and while it is checking for new mail, use the down arrow to go through messages. Eventually it stops, the machine uses a full core and a few seconds later evolution closes.

[Apport retracing service (apport)]

StacktraceTop:?? ()
destroy_closure_array (data=0xa10ff30)
IA__g_datalist_id_set_data_full (datalist=0x9fbc2c8,
g_object_real_dispose (object=0x9fbc2c0)
gtk_object_dispose (gobject=0x9fbc2c0)

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Sebastien Bacher (seb128)]

those recent crashers could be the same cause, there is http://bugzilla.gnome.org/show_bug.cgi?id=578685 open already about a crash

[Sebastien Bacher (seb128)]

the issue is probably bug #358223, closing as duplicate, you can reopen if you still get the issue once the other bug is closed

[dieterv (dieterv77)]

Thanks Sebastian for your time.
FYI, i tried to produce the crash with valgrind but did not succeed (much like the reported of the other bug).
i'll keep on eye on the other bug and make sure things work fine once it is fixed.