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 794228 - epiphany-search-provider killed by SIGSEGV
epiphany-search-provider killed by SIGSEGV
Status: RESOLVED NOTGNOME
Product: epiphany
Classification: Core
Component: General
3.26.x
Other Linux
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-03-10 17:42 UTC by sirredbeard
Modified: 2018-03-22 16:39 UTC
See Also:
GNOME target: ---
GNOME version: 3.25/3.26

Attachments
Screenshot (72.32 KB, image/png)
2018-03-10 17:42 UTC, sirredbeard 		Details
backtrace (24.18 KB, application/octet-stream)
2018-03-10 17:42 UTC, sirredbeard 		Details
core backtrace (20.67 KB, application/octet-stream)
2018-03-10 17:43 UTC, sirredbeard 		Details
environ (1.53 KB, application/octet-stream)
2018-03-10 17:44 UTC, sirredbeard 		Details
exploitable (82 bytes, application/octet-stream)
2018-03-10 17:45 UTC, sirredbeard 		Details
os_info (596 bytes, application/octet-stream)
2018-03-10 17:45 UTC, sirredbeard 		Details

Description sirredbeard 2018-03-10 17:42:00 UTC 
Created attachment 369534 [details]
Screenshot

epiphany-search-provider is crashing pretty regularly on the backend.

My search provider is set to DuckDuckGo.

I can't get gnome-abrt to generate a decent report, so I attached everything here.
Comment 1 sirredbeard 2018-03-10 17:42:54 UTC 
Created attachment 369535 [details]
backtrace
Comment 2 sirredbeard 2018-03-10 17:43:58 UTC 
Created attachment 369536 [details]
core backtrace
Comment 3 sirredbeard 2018-03-10 17:44:50 UTC 
Created attachment 369537 [details]
environ
Comment 4 sirredbeard 2018-03-10 17:45:09 UTC 
Created attachment 369538 [details]
exploitable
Comment 5 sirredbeard 2018-03-10 17:45:43 UTC 
Created attachment 369539 [details]
os_info
Comment 6 Michael Catanzaro 2018-03-10 17:51:24 UTC 
This is surely https://bugs.webkit.org/show_bug.cgi?id=176490.

Thanks for attaching a backtrace, but for future reference you should install debuginfo first. gdb should have printed out debuginfo-install command that you could have run to install all the needed packages. Your trace shows this stack for the crashing thread:

+ Trace 238468

Thread 1 (Thread 0x7f60b9acc3c0 (LWP 22858))

  • #0 ??
    from /lib64/libwayland-client.so.0
  • #1 ?? 

which would be useless if I didn't recognize this as https://bugs.webkit.org/show_bug.cgi?id=176490. Anyway, thanks again for reporting
Comment 7 Michael Catanzaro 2018-03-11 02:08:44 UTC 
I posted a new patch in the WebKit issue. I had another one several months ago, but it was more of a workaround (albeit one that makes sense to do anyway) and was not accepted.
Comment 8 sirredbeard 2018-03-22 16:39:40 UTC 
(In reply to Michael Catanzaro from comment #6)
> This is surely https://bugs.webkit.org/show_bug.cgi?id=176490.
> 

Thanks. Not sure why debuginfo was not installed.