After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 657404 - Repeatable evolution hang
Repeatable evolution hang
Status: RESOLVED OBSOLETE
Product: tracker
Classification: Core
Component: Miners
0.12.x
Other Linux
: Normal critical
: ---
Assigned To: tracker-general
Jamie McCracken
Depends on:
Blocks:
 
 
Reported: 2011-08-26 06:42 UTC by Milan Crha
Modified: 2021-05-26 22:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan Crha 2011-08-26 06:42:56 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=733523

Description of problem:
I recently added a second account to my Evolution setup, both with IMAP servers
(not IMAP+, just vanilla IMAP).  Since then, Evolution has hung every single
day; I don't know if there is a causal relationship.  It usually runs for
several hours before hanging; I typically notice the hang an hour or two before
quitting time.

I'll attach a backtrace of both the stuck Evolution process, and the only other
evolution-related process I see running, which is evolution-alarm-notify.

Version-Release number of selected component (if applicable):
evolution-3.0.2-3.fc15.x86_64

How reproducible:
About once per day.

Steps to Reproduce:
1. Start evolution first thing in the morning.
2. Wait.
3.

Actual results:
Evolution eventually hangs.

Expected results:
Evolution should never hang.

Additional info:
Sometimes it is doing nothing when the hang occurs.  The backtrace I'm
attaching, though, is for an Evolution that shows one "Scanning folders in IMAP
server foo' and one "Pinging IMAP server foo" message on the bottom.  Should it
be scanning folders in an IMAP server that it is also pinging?

[Thread debugging using libthread_db enabled]
[New Thread 0x7f7b15bf0700 (LWP 28268)]
[New Thread 0x7f7b17fff700 (LWP 28227)]
[New Thread 0x7f7b398a1700 (LWP 28219)]
[New Thread 0x7f7b3beeb700 (LWP 28218)]
[New Thread 0x7f7b292b3700 (LWP 28217)]
[New Thread 0x7f7b16bf2700 (LWP 28216)]
[New Thread 0x7f7b163f1700 (LWP 28215)]
[New Thread 0x7f7b28ab2700 (LWP 24956)]
[New Thread 0x7f7b49e95700 (LWP 20001)]

warning: "/usr/lib/debug/usr/lib64/libicudata.so.44.2.debug": separate debug info file has no debug info
__lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:140
140	2:	movl	%edx, %eax

Thread 1 (Thread 0x7f7b50f409a0 (LWP 20000))

  • #0 __lll_lock_wait
    at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S line 140
  • #1 _L_lock_752
    from /lib64/libpthread.so.0
  • #2 __pthread_mutex_lock
    at pthread_mutex_lock.c line 65
  • #3 g_source_attach
    at gmain.c line 963
  • #4 g_idle_add_full
    at gmain.c line 4620
  • #5 mail_msg_idle_cb
    at mail-mt.c line 390
  • #6 g_main_dispatch
    at gmain.c line 2441
  • #7 g_main_context_dispatch
    at gmain.c line 3014
  • #8 g_main_context_iterate
    at gmain.c line 3092
  • #9 g_main_loop_run
    at gmain.c line 3300
  • #10 gtk_main
    at gtkmain.c line 1358
  • #11 main
    at main.c line 734

Comment 1 Jerry James 2011-10-15 17:29:40 UTC
Here's a possibly critical bit of information.  I uninstalled tracker-evolution-plugin last week because of some misbehavior that was causing me trouble, and the hangs suddenly stopped.  I have left Evolution running continuously for the last several days, and no hang, where before it would hang after only a few hours.  So the tracker plugin appears to be the culprit, not Evolution itself.
Comment 2 Matthew Barnes 2011-10-15 17:51:22 UTC
Okay, we'll assume this is tracker then.
Comment 3 Martyn Russell 2011-12-07 09:17:37 UTC
CCing our recent Evo <-> Tracker rockstar ;)
Comment 4 Milan Crha 2011-12-07 09:28:27 UTC
I would start with changes from bug #644695 at the first place, as that can do pretty anything afterwards. The backtrace itself is kinda clean otherwise.
Comment 5 Sam Thursfield 2021-05-26 22:24:01 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new enhancement request ticket at
  https://gitlab.gnome.org/GNOME/tracker/-/issues/

Thank you for your understanding and your help.