evolution crash while opening groupwise appointment

Bug #315377 reported by gunny26
2
Affects Status Importance Assigned to Milestone
Evolution
Fix Released
High
evolution (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

When opening an groupwise appointment evolution will
start to consume all available memory, then terminate.

In inbox i click on this message/appointment, a new windows will open,
and the only message wich appear is "Message will be formatted"
( in german version this is "Nachricht wird formatiert" ).
Then memory consumption begins to rise, and evolution process will consume all available memory.

output on cole is:
-----------------
(evolution:6954): e-utils-CRITICAL **: e_plugin_invoke: assertion `ep->enabled' failed
evolution-shell-Message: Killing old version of evolution-data-server...

(evolution:6954): camel-groupwise-provider-WARNING **: Could not connect..failure connecting

(evolution:6954): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed

(evolution:6954): camel-CRITICAL **: camel_store_get_folder: assertion `CAMEL_IS_STORE (store)' failed

(evolution:6954): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed

(evolution:6954): evolution-mail-CRITICAL **: mail_tools_folder_to_url: assertion `CAMEL_IS_FOLDER (folder)' failed

(evolution:6954): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed

(evolution:6954): camel-CRITICAL **: camel_store_get_folder: assertion `CAMEL_IS_STORE (store)' failed

(evolution:6954): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed

(evolution:6954): evolution-mail-CRITICAL **: mail_tools_folder_to_url: assertion `CAMEL_IS_FOLDER (folder)' failed

(evolution:6954): libegroupwise-WARNING **: e-gw-container.c:208: found container with no name

(evolution:6954): libegroupwise-CRITICAL **: e_gw_container_get_total_count: assertion `E_IS_GW_CONTAINER (container)' failed

(evolution:6954): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(evolution:6954): camel-WARNING **: No from set for message

Number of items in the folder: 83

GLib-ERROR **: /build/buildd/glib2.0-2.18.2/glib/gmem.c:156: failed to allocate 219031 bytes
aborting...
Aborted
-----------------

i have appended a valgrind log made with this command line:
valgrind --trace-children=yes --log-file=evolution_appointment_%p.log evolution

Revision history for this message
gunny26 (arthur-messner) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
gunny26 (arthur-messner) wrote :

i followed the instructions of the backtrace documention,
but at
---
(gdb) backtrace full
---
the output seems to be in loop, so i killed evolution after about 5 min.

i attached the output file so far

Revision history for this message
Sebastien Bacher (seb128) wrote :

the valgrind log has an error but lacks debug information, could you install evolution-data-server-dbg and get a new log?

Revision history for this message
Sebastien Bacher (seb128) wrote :

the valgrind log is similar to http://bugzilla.gnome.org/show_bug.cgi?id=531509 which is supposed to fixed in the current intrepid updates version, closing the bug, you can reopen if you still get the issue though

Changed in evolution:
status: Incomplete → Fix Released
Changed in evolution:
status: Unknown → Fix Released
Changed in evolution:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.