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 783022 - random crash (SIGSEGV)
random crash (SIGSEGV)
Status: RESOLVED DUPLICATE of bug 773420
Product: evolution
Classification: Applications
Component: Composer
3.22.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2017-05-24 01:38 UTC by Paul Wise
Modified: 2017-05-30 09:02 UTC
See Also:
GNOME target: ---
GNOME version: 3.21/3.22

Attachments
gdb backtrace of the crash (101.90 KB, text/plain)
2017-05-24 01:38 UTC, Paul Wise 		Details

Description Paul Wise 2017-05-24 01:38:47 UTC 
Created attachment 352466 [details]
gdb backtrace of the crash

I got a random crash (SIGSEGV) in evolution. I am using evolution 3.22.6-1, evolution-data-server 3.22.7-1 and GNOME 3.22 on Debian stretch. If the below gdb backtrace summary and attached full gdb backtrace isn't useful, please close this bug.

Core was generated by `evolution'.
Program terminated with signal SIGSEGV, Segmentation fault.

+ Trace 237505

  • #0 strlen
    at ../sysdeps/x86_64/strlen.S line 106
  • #0 strlen
    at ../sysdeps/x86_64/strlen.S line 106
  • #1 composer_build_message
  • #2 e_msg_composer_get_message_draft
    at e-msg-composer.c line 5218
  • #3 save_snapshot_replace_cb
    at e-autosave-utils.c line 331
  • #4 g_task_return_now
    at ././gio/gtask.c line 1121
  • #5 complete_in_idle_cb
    at ././gio/gtask.c line 1135
  • #6 g_main_dispatch
    at ././glib/gmain.c line 3203
  • #7 g_main_context_dispatch
    at ././glib/gmain.c line 3856
  • #8 g_main_context_iterate
    at ././glib/gmain.c line 3929
  • #9 g_main_loop_run
    at ././glib/gmain.c line 4125
  • #10 gtk_main
    at ././gtk/gtkmain.c line 1312
  • #11 main
    at main.c line 665 






Comment 1


Milan Crha





          2017-05-30 09:02:32 UTC
        



Thanks for a bug report. This is already filled as bug #773420. A workaround is committed, but the real cause for it is not known yet. Any help in this regard would be appreciated, though in the case of the crashed evolution it's pretty hard to figure out what corresponding WebKitWebProcess does. Please see the other bug report for more details.

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