epiphany-search-provider crashed with SIGSEGV in wl_list_insert_list()

[Daniel]

After the first restart after upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10 I got this crash report.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: epiphany-browser 3.26.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Oct 20 20:21:06 2017
ExecutablePath: /usr/lib/epiphany-search-provider
InstallationDate: Installed on 2017-04-07 (196 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
ProcCmdline: /usr/lib/epiphany-search-provider
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f2d35869e30 <wl_list_insert_list+32>: mov %rbp,(%rax)
 PC (0x7f2d35869e30) ok
 source "%rbp" ok
 destination "(%rax)" (0x00000005) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: epiphany-browser
StacktraceTop:
 wl_list_insert_list () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0
 () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0
 wl_display_destroy () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0
 () at /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 () at /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
Title: epiphany-search-provider crashed with SIGSEGV in wl_list_insert_list()
UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

[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 #1716208, 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.