RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
The bug seems to be triggered by similar actions as the one with different backtrace:
1. open mail window
2. open calendar winow
3. go offline
4. go online

after some time, evo crashes.

# grep -v '^$\|^#' /etc/sysconfig/debug 
export MALLOC_CHECK_=1
export MALLOC_PERTURB_=$(($RANDOM % 255 + 1))
export G_SLICE=always-malloc,debug-blocks

$ echo $MALLOC_CHECK_ ; echo $MALLOC_PERTURB_ ; echo $G_SLICE
1
216
always-malloc,debug-blocks


Version-Release number of selected component:
evolution-2.28.3-30.el6

Additional info:
libreport version: 2.0.9
abrt_version:   2.0.8
backtrace_rating: 4
cmdline:        evolution -c mail
crash_function: camel_msgport_try_pop
kernel:         2.6.32-356.el6.x86_64

truncated backtrace:
:Thread no. 1 (5 frames)
: #0 camel_msgport_try_pop at camel-msgport.c
: #1 camel_operation_cancel_check at camel-operation.c
: #2 regen_list_done at message-list.c
: #3 mail_msg_idle_cb at mail-mt.c
: #8 bonobo_main at bonobo-main.c

Created attachment 697179 [details]
File: maps

Created attachment 697180 [details]
File: var_log_messages

Created attachment 697181 [details]
File: open_fds

Created attachment 697182 [details]
File: environ

Created attachment 697183 [details]
File: dso_list

Created attachment 697184 [details]
File: limits

Created attachment 697185 [details]
File: sosreport.tar.xz

Created attachment 697186 [details]
File: backtrace

Created attachment 697187 [details]
File: build_ids

Created attachment 697188 [details]
File: cgroup

Thanks for a bug report. This is the same as bug #602667. Feel free to reopen it and/or test the patch provided there. I'm marking this as a duplicate of it.

*** This bug has been marked as a duplicate of bug 602667 ***