evolution-addressbook-factory-subprocess crashed with SIGSEGV in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string()

[Adrian Scripcă]

It just crashed

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: evolution-data-server 3.26.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 25 12:33:26 2017
ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory-subprocess
InstallationDate: Installed on 2015-12-17 (678 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory-subprocess --factory google --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx3313x4 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/3313/4
SegvAnalysis:
 Segfault happened at: 0x7f860285b0db <_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC2ERKS4_+11>: mov (%rsi),%rax
 PC (0x7f860285b0db) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution-data-server
Title: evolution-addressbook-factory-subprocess crashed with SIGSEGV in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string()
UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
UserGroups: adm audio cdrom dialout dip docker input lpadmin plugdev sambashare sudo tty wireshark

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1725114, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.