GNOME Bugzilla – Bug 638808
camel_shutdown() called too early
Last modified: 2018-12-12 14:54:15 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=665929 abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: evolution component: evolution crash_function: PK11_DestroySlot executable: /usr/bin/evolution kernel: 2.6.35.10-72.fc14.i686.PAE package: evolution-2.32.1-1.fc14 rating: 4 reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1293497778 uid: 500 How to reproduce ----- 1. Open Evolution 2. Work for 10 hours 3. Close Evolution and Crash Core was generated by `evolution'. Program terminated with signal 11, Segmentation fault.
+ Trace 225424
Thread 1 (Thread 2510)
After Dan Williams' investigation at https://bugzilla.redhat.com/show_bug.cgi?id=657254 it turned out that camel_shutdown() is called too early, which is causing crashes like this. See the downstream bug for more details.
Created attachment 178010 [details] [review] evo patch for evolution; Calls camel_shutdown() only after the EMailBackend is finalized, and actually frees backends on EShell finalize too, so this all can safely work.
Created commit 28c3b67 in evo master (2.91.6+) Created commit 9f76afb in evo gnome-2-32 (2.32.2+)
A user from the downstream bug requested reopening this, because he sees the issue in 2.32.2, thus I'm doing so. https://bugzilla.redhat.com/show_bug.cgi?id=657254#c13
And here is one from 3.2.2: https://bugzilla.redhat.com/show_bug.cgi?id=759185 libreport version: 2.0.7 abrt_version: 2.0.6 backtrace_rating: 4 cmdline: evolution comment: I Closed Evolution? It seemed to have crashed on close. crash_function: pk11_Finalize executable: /usr/bin/evolution kernel: 3.1.2-1.fc16.x86_64 pid: 2748 reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) time: Thu 01 Dec 2011 11:05:09 AM EST Core was generated by `evolution'. Program terminated with signal 11, Segmentation fault.
+ Trace 229201
Thread 3 (Thread 0x7f91cf51e700 (LWP 2750))
Same as from 3.4.4: https://bugzilla.redhat.com/show_bug.cgi?id=892640
I've just got a duplicate from 3.10.4, at https://bugzilla.redhat.com/show_bug.cgi?id=1068984 Thinking of it, this might be fixed, as a side effect, by commits: https://git.gnome.org/browse/evolution/commit/?id=197c8e1274f70c035614 https://git.gnome.org/browse/evolution/commit/?id=967d37373f5e59a46203 which were done for 3.12.0.
I'm closing this, but feel free to reopen or comment in case you can reproduce with the current 3.30.x stable series.