Ubuntu
evolution package

Evolution freezes often [evolution crashed with SIGSEGV in __kernel_vsyscall() ]

Bug #527569 reported by Vish on 2010-02-25

This bug affects 5 people

Affects		Status	Importance	Assigned to	Milestone
	Evolution	Fix Released	Critical	gnome-bugs #613693
	evolution (Ubuntu)	Fix Released	Medium	Unassigned

Bug Description

Binary package hint: evolution

I find evolution often frozen and using high CPU.

I keep evolution running constantly and I have noticed this behavior often.
The freeze is aways during the fetching of mails. I notice the status bar stuck at "Fetching mail...." and evolution consuming high cpu for a very long time. [Not sure how to consistently reproduce it.]

This time evolution froze when I manually clicked send/receive button.
I used $ kill -11 <evolution PID> to generate this report.

[this bug , has been happening for 2-3 weeks and is unrelated to the gtk-csd change which seems fixed]

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 6c350872f0b430ef8235c693ed2354c1
CheckboxSystem: 5484a8dd99f006173bd2ac53fa4837c2
CrashCounter: 1
Date: Thu Feb 25 11:06:44 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
Package: evolution 2.28.2-1ubuntu6
ProcCmdline: evolution
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SegvAnalysis:
Segfault happened at: 0x528422 <__kernel_vsyscall+2>: ret
PC (0x00528422) ok
Reason could not be automatically determined.
Signal: 11
SourcePackage: evolution
StacktraceTop:
__kernel_vsyscall ()
*__GI___poll (fds=0x65bdff4, nfds=10, timeout=124)
g_poll () from /lib/libglib-2.0.so.0
?? () from /lib/libglib-2.0.so.0
g_main_loop_run () from /lib/libglib-2.0.so.0
Title: evolution crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux 2.6.32-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Vish (vish) wrote on 2010-02-25:

Dependencies.txt Edit (6.5 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (385 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (69.8 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (785 bytes, text/plain; charset="utf-8")
Registers.txt Edit (479 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (22.4 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (138.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2010-02-25:

StacktraceTop:
__kernel_vsyscall ()
*__GI___poll (fds=0x65bdff4, nfds=10, timeout=124)
g_poll () from /lib/libglib-2.0.so.0
?? () from /lib/libglib-2.0.so.0
g_main_loop_run () from /lib/libglib-2.0.so.0

Revision history for this message

Apport retracing service (apport) wrote on 2010-02-25: Stacktrace.txt

Stacktrace.txt Edit (822 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2010-02-25: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (18.2 KiB, text/plain)

Changed in evolution (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Vish (vish) on 2010-03-01

tags:	added: regression-potential
visibility:	private → public

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2010-03-18:

Hello Vish, Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in evolution (Ubuntu):
assignee:	nobody → Ubuntu Desktop Bugs (desktop-bugs)
status:	New → Incomplete

Pedro Villavicencio (pedro) on 2010-03-18

Changed in evolution (Ubuntu):
assignee:	Ubuntu Desktop Bugs (desktop-bugs) → nobody

Revision history for this message

Vish (vish) wrote on 2010-03-21:

gdb-evolution.txt Edit (229.1 KiB, text/plain)

Kept running evolution in gdb to finally catch it in action.

Noticed that evolution had frozen with:
Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 0xacd9cb70 (LWP 16296)]
0x0012d422 in __kernel_vsyscall ()

But no high CPU usage , it was just frozen this time at "Fetching mail..."

Retrieved the gdb , attaching

Changed in evolution (Ubuntu):
status:	Incomplete → New

Revision history for this message

Vish (vish) wrote on 2010-03-21:

I think the no high CPU was due to evolution running in gdb.
Since, i noticed that it always uses high CPU whenever it freezes with "Fetching Mail..".

Revision history for this message

Vish (vish) wrote on 2010-03-22:

gdbattach-evolution.txt Edit (47.3 KiB, text/plain)

Again found evolution frozen at "Fetching Mail..." and using high CPU:
This time i used the attach option for the backtrace mentioned here > [https://wiki.ubuntu.com/Backtrace#Already%20running%20programs] [I had to skip the "(gdb) continue" part since the program had already frozen]

Attaching the backtrace retrieved.

Revision history for this message

Vish (vish) wrote on 2010-03-23:

fullgdb-evolution.txt Edit (43.1 KiB, text/plain)

Did another debug. I think this has all the debug symbols.

I dont see "??" anywhere.

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2010-03-23:

#10

There's no exact match for the backtrace upstream (at least didn't find anything similar), I've sent this upstream at: https://bugzilla.gnome.org/show_bug.cgi?id=613693 ; Thanks for your work on getting the backtrace Vish.

Changed in evolution (Ubuntu):
status:	New → Triaged

Revision history for this message

Vish (vish) wrote on 2010-03-24:

#11

Looks like upstream wants to use "(gdb) handle SIGPIPE pass nostop noprint"

Will be getting gdb for that as well

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2010-03-25:

#12

Thanks Vish.

Revision history for this message

Vish (vish) wrote on 2010-03-25:

#13

gdb-evolution-SIGPIPE.txt Edit (122.0 KiB, text/plain)

gdb from (gdb) handle SIGPIPE pass nostop noprint

Revision history for this message

Vish (vish) wrote on 2010-03-26:

#14

evo.txt Edit (59.0 KiB, text/plain)

Another gdb, with no "??" attached this to upstream as well.

Revision history for this message

Vish (vish) wrote on 2010-04-05:

#15

Sebastien Bacher mentioned that this might be due to keyring problems and
Since update libgnome-keyring (2.30.0-0ubuntu3) for Bug #530605
---------------
libgnome-keyring (2.30.0-0ubuntu3) lucid; urgency=low

  * debian/patches/02_workaround_cpu_use.patch:
    - change from https://bugzilla.gnome.org/show_bug.cgi?id=606902
      to try to workaround extra cpu use issues (lp: #530605)
-- Sebastien Bacher <email address hidden> Thu, 01 Apr 2010 15:58:01 +0200

I'v been seeing less of this bug , rather I havent seen the bug since the update.

Or it might be update evolution (2.28.3-0ubuntu7) to 2.28.3-0ubuntu8 , both happened on the same day :s

Not sure if it fixes this issue , since this was a *randomly occurring bug* .
Still watching , will report back after a few more days of testing

Revision history for this message

Vish (vish) wrote on 2010-04-15:

#16

I'v been watching for any signs of this bug , but this hasnt occurred even once since 15days , either the gkd fix solved this too or new evolution has solved this bug.

Marking bug as fixed.

Changed in evolution (Ubuntu):
status:	Triaged → Fix Released

Bug Watch Updater (bug-watch-updater) on 2010-04-16

Changed in evolution:
status:	Unknown → Fix Released

Bug Watch Updater (bug-watch-updater) on 2010-09-16

Changed in evolution:
importance:	Unknown → Critical

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #530035

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

gnome-bugs #606902
[RESOLVED FIXED] Edit
gnome-bugs #613693
[RESOLVED FIXED] Edit

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

Ubuntuevolution package

Evolution freezes often [evolution crashed with SIGSEGV in __kernel_vsyscall() ]

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
evolution package