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 730134 - Segmentation fault: camel-ews-store.c: No such file or directory
Segmentation fault: camel-ews-store.c: No such file or directory
Status: RESOLVED FIXED
Product: evolution-ews
Classification: Other
Component: Mail
3.12.x
Other Linux
: Normal critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2014-05-14 14:19 UTC by Robert Munteanu
Modified: 2014-05-16 20:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Robert Munteanu 2014-05-14 14:19:16 UTC 
I recently updated from 3.10.4 to 3.12.1 . After a small period of time ( minutes ) , evolution crashed. Started it under gdb and got

Program received signal SIGSEGV, Segmentation fault.

+ Trace 233598

Thread 140734460061440 (LWP 6269)

  • #0 camel_ews_folder_update_thread
    at camel-ews-store.c line 755
  • #1 g_thread_proxy
    at gthread.c line 764
  • #2 start_thread
    at pthread_create.c line 309
  • #3 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 111 

There are also lots of assertion failed lines logged to the console

(evolution:6136): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed
Comment 1 Fabiano Fidêncio 2014-05-15 08:49:37 UTC 
(In reply to comment #0)
> I recently updated from 3.10.4 to 3.12.1 . After a small period of time (
> minutes ) , evolution crashed. Started it under gdb and got

May I ask you to install debug packages for you distro and try to reproduce it again?
And, please, when it crashes, get the backtrace of all threads running. You can do it using, in gdb, instead of "bt", "t a a bt" (thread apply all backtrace)

>There are also lots of assertion failed lines logged to the console

>(evolution:6136): GLib-GObject-CRITICAL **: g_closure_unref: assertion
>'closure->ref_count > 0' failed

Yeah, it's happening when you have a "new" version of WebKit.
I'm pretty sure this is not the reason of your crash.
Comment 2 Fabiano Fidêncio 2014-05-15 09:25:51 UTC 
Aha!

I see, Milan Crha cooked a patch for this and it's already upstream, it is in 3.12.2+ (see: https://git.gnome.org/browse/evolution-ews/commit/?h=evolution-ews-3-12&id=331ec86473aec5a62362c79de66f522a4eea68ab)

I'm closing this bug as FIXED.
Comment 3 Robert Munteanu 2014-05-15 09:27:06 UTC 
That was fast, thanks!. I'll retest with 3.12.3 then .
Comment 4 Milan Crha 2014-05-15 14:30:04 UTC 
(In reply to comment #3)
> That was fast, thanks!. I'll retest with 3.12.3 then .

It's 3.12.2 inclusive and following releases, thus you do not need to wait that long. :)
Comment 5 Robert Munteanu 2014-05-16 20:34:02 UTC 
(In reply to comment #4)
> It's 3.12.2 inclusive and following releases, thus you do not need to wait that
> long. :)

Great, thanks. Fingers crossed for the update to hit the openSUSE repos soon.