GNOME Bugzilla – Bug 341386
Crashed in camel-object.c:1034 camel_object_is() ?
Last modified: 2009-11-27 11:10:24 UTC
Steps to reproduce: 1. Clicked on a message 2. Clicked on the down arrow to get the menu to save the attachment. 3. Crashed. Restarted evolution and i did not see the problem again. Stack trace: Backtrace was generated from '/opt/gnome2/bin/evolution-2.8' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1233164624 (LWP 32381)] [New Thread -1353847904 (LWP 32557)] [New Thread -1395811424 (LWP 32554)] [New Thread -1446167648 (LWP 32553)] [New Thread -1420989536 (LWP 32552)] [New Thread -1362240608 (LWP 32551)] [New Thread -1353581664 (LWP 32387)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 68163
Thread 1 (Thread -1233164624 (LWP 32381))
Other information:
Chen: is this a consistently reproducible bug bcoz u have marked it as critical. If so attach that message or mail that message to maileer maintainers. I am not able to reproduce this bug.
poornima: crashes are always critical per definition. see http://bugzilla.gnome.org/page.cgi?id=bug-status.html#bug_severity perfect stacktrace with line numbers, no idea why you set this to NEEDINFO at all.
*** Bug 480681 has been marked as a duplicate of this bug. ***
*** Bug 455164 has been marked as a duplicate of this bug. ***
*** Bug 476878 has been marked as a duplicate of this bug. ***
Bumping version due to the dups being on 2.10.
*** Bug 480856 has been marked as a duplicate of this bug. ***
*** Bug 487145 has been marked as a duplicate of this bug. ***
0) crash is (of course) in Thread 1:
+ Trace 210889
The culprit seems to be this line in mail/em-format-html-display.c:efhd_attachment_popup(): target = em_popup_target_new_part(emp, info->puri.part, info->handle?info->handle->mime_type:NULL); which in this case is apparently called with info->puri == NULL 2) So a solution could be to simply prepend this line: if (!info->puri) return FALSE; 3) Not tested my analysis at all. Seems a race condition at first glance, so without further pinpointing of crashing behaviour, testing is not easy at all.
@ Chen - Did you get similar crash any time later ? Does Null check mentioned in comment#9 help in preventing the crash ? If you cann't reproduce on current master or 2.26.x, we should close the bug, tia.
Closing this bug report as no further information has been provided. Please feel free to reopen the bug if the problem still occurs with a newer version of GNOME 2.28.0 or later, thanks.