Description of problem: It crashed when I changed the default search engine from duckduckGo to Google and tried to search from the URL bar Version-Release number of selected component: epiphany-runtime-1:48.5-1.fc42 Additional info: reporter: libreport-2.17.15 type: CCpp reason: epiphany killed by SIGABRT journald_cursor: s=340560ff638e466786d4bdb6f606e584;i=45f954;b=abdf83060b3d4f9fa6673588e36f714d;m=106095d0f;t=63ff0d4fa2c80;x=2da6c539f2e0de89 executable: /usr/bin/epiphany cmdline: /usr/bin/epiphany cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.Software rootdir: / uid: 1000 kernel: 6.16.8-200.fc42.x86_64 package: epiphany-runtime-1:48.5-1.fc42 runlevel: N 5 dso_list: /usr/bin/epiphany epiphany-runtime-1:48.5-1.fc42.x86_64 (Fedora Project) 1756089958 backtrace_rating: 4 crash_function: WTFCrashWithInfo comment: It crashed when I changed the default search engine from duckduckGo to Google and tried to search from the URL bar Truncated backtrace: Thread no. 1 (2 frames) #4 WTFCrashWithInfo at WTF/Headers/wtf/Assertions.h:972 #5 WebKit::FenceMonitor::addFileDescriptor at /usr/src/debug/webkitgtk-2.50.0-1.fc42.x86_64/Source/WebKit/UIProcess/glib/FenceMonitor.cpp:104
Created attachment 2108106 [details] File: proc_pid_status
Created attachment 2108107 [details] File: maps
Created attachment 2108108 [details] File: limits
Created attachment 2108109 [details] File: environ
Created attachment 2108110 [details] File: open_fds
Created attachment 2108111 [details] File: mountinfo
Created attachment 2108112 [details] File: os_info
Created attachment 2108113 [details] File: cpuinfo
Created attachment 2108114 [details] File: core_backtrace
Created attachment 2108115 [details] File: backtrace
There are two bugs here: * AcceleratedBackingStore::frame passed an invalid WTF::UnixFileDescriptor to FenceMonitor::addFileDescriptor. Why is the fd invalid? * This is an IPC interface; the fd is sent from the web process to the UI process, and it's expected that the message may be malicious and invalid. The UI process should message check it and kill the web process if the message is invalid. It shouldn't be possible for anything the web process does to crash the UI process. I will forward this to upstream WebKit Bugzilla.