Bug 1768089

Summary: [abrt] epiphany: g_error_free(): epiphany-search-provider killed by SIGABRT
Product: [Fedora] Fedora Reporter: Chen_Min_Chin <tcfxfzoi>
Component: epiphanyAssignee: Michael Catanzaro <mcatanzaro>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: contbogus, gecko-bugs-nobody, gnome-sig, j.hoffmann, jhorak, john.j5live, mcatanzaro, mclasen, phatina, rhughes, rstrode, sandmann, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3860d98bf486765481dd7e15acec3e6474d025ef
Whiteboard: abrt_hash:de2b1e37d424a6cb07b4113f13294eaa283cc27a;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-16 21:05:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Chen_Min_Chin 2019-11-02 12:35:22 UTC 
Version-Release number of selected component:
1:epiphany-3.34.1-1.fc31

Additional info:
reporter:       libreport-2.10.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/dbus\x2d:1.2\x2dorg.gnome.Epiphany.SearchProvider.slice/dbus-:1.2-org.gnome.Epiphany.SearchProvider
cmdline:        /usr/libexec/epiphany-search-provider
crash_function: g_error_free
executable:     /usr/libexec/epiphany-search-provider
journald_cursor: s=0d51de3cdc1e4e6a9da36b6d0a968675;i=aa7c7;b=1b843d0adca74e20afc1cffbd9754cdd;m=4816acd43;t=5965bed64652e;x=10511ed20b0f9304
kernel:         5.3.7-301.fc31.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 1 Chen_Min_Chin 2019-11-02 12:35:27 UTC 
Created attachment 1631829 [details]
File: backtrace
Comment 2 Chen_Min_Chin 2019-11-02 12:35:29 UTC 
Created attachment 1631830 [details]
File: core_backtrace
Comment 3 Chen_Min_Chin 2019-11-02 12:35:30 UTC 
Created attachment 1631831 [details]
File: cpuinfo
Comment 4 Chen_Min_Chin 2019-11-02 12:35:32 UTC 
Created attachment 1631832 [details]
File: dso_list
Comment 5 Chen_Min_Chin 2019-11-02 12:35:33 UTC 
Created attachment 1631833 [details]
File: environ
Comment 6 Chen_Min_Chin 2019-11-02 12:35:35 UTC 
Created attachment 1631834 [details]
File: limits
Comment 7 Chen_Min_Chin 2019-11-02 12:35:37 UTC 
Created attachment 1631835 [details]
File: maps
Comment 8 Chen_Min_Chin 2019-11-02 12:35:40 UTC 
Created attachment 1631836 [details]
File: mountinfo
Comment 9 Chen_Min_Chin 2019-11-02 12:35:41 UTC 
Created attachment 1631837 [details]
File: open_fds
Comment 10 Chen_Min_Chin 2019-11-02 12:35:43 UTC 
Created attachment 1631838 [details]
File: proc_pid_status
Comment 11 Michael Catanzaro 2019-11-02 13:25:29 UTC 
Hi, any chance you have some idea of how to reproduce this?

I see 316 reports and from 174 users on FAF, which is a lot. But the backtrace indicates memory corruption and the crashing code is clearly innocent, so it's not actionable without using valgrind or an asan build. Starting a search provider with valgrind will be slightly awkward as we'll need to edit the D-Bus service file, but if we know how to reproduce the crash then that will be worth doing.
Comment 12 Jobst Hoffmann 2019-12-13 18:34:24 UTC 
*** Bug 1783431 has been marked as a duplicate of this bug. ***
Comment 13 Michael Catanzaro 2019-12-16 20:57:35 UTC 
Hm, we have thousands of reports of this, all occurring in exactly the same place. It would be weird for this to be memory corruption from somewhere else, like I had been thinking. Maybe something is wrong with the error returned by ephy_bookmarks_manager_save_sync().

The crash probably only occurs when you have no ~/.local/share/bookmarks.gvdb, so deleting that file is going to be a requirement to reproduce, but that doesn't seem sufficient.
Comment 14 Michael Catanzaro 2019-12-16 21:05:13 UTC 
OK, this turned out to be a simple problem. Sorry I didn't notice the first time I looked at it. This will be solved in 3.34.3.
Comment 15 contbogus 2019-12-31 19:18:39 UTC 
*** Bug 1787172 has been marked as a duplicate of this bug. ***