Bug 254527

Summary: [Gtk] WebKit crashed repeatingly
Product: WebKit Reporter: Peter <peter.weber>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Major CC: bugs-noreply, mcatanzaro
Priority: P2    
Version: Safari 15   
Hardware: PC   
OS: Linux   
Attachments:
Description Flags
stacktrace from gdb
none
output from journalctl (same a stacktrace)
none
output from journalctl (other system -> AMD GCN) none

Description Peter 2023-03-27 09:11:39 PDT
Created attachment 465610 [details]
stacktrace from gdb

Hello!

Since a recent upgrade (~ four weeks) Epiphany is crashing randomly and subsequent repeatingly on the same website. It is enough the browse rather simple websites like "archlinux.org".

System: Archlinux
Update: 2023-03-27 (all updates)
Windowing: Wayland, GNOME with Mutter
Hardware: ThinkPad X220 with Intel Sandy Bridge (HD3000)

Steps to reproduce:
1.) Open various websites within tabs {archlinux.org, stackoverflow.com, webkit.org, ...}
2.) After approximately 15 minutes of active browsing one of this websites will crash the web-browser
3.) GNOME will ask "Terminate or Keep" # selection doesn't matter
4.) From now on Epiphany will crash every time on the website which caused the crash, until reboot

I've set severity to "Major" because Epiphany is barely usable.

Stacktrace attached, created as following after core dump:
1. $ coredumbctl gdb
2. gdb and debuginfo does its work :)
3. gdb instructions
(gdb) set logging file trace.log
(gdb) set logging enabled on
(gdb) thread apply all bt full
(gdb) set logging enabled off
(gdb) quit

Thank you
If you need more info, tell me.
Comment 1 Peter 2023-03-27 09:17:45 PDT
Created attachment 465611 [details]
output from journalctl (same a stacktrace)
Comment 2 Peter 2023-03-27 09:19:20 PDT
Created attachment 465612 [details]
output from journalctl (other system -> AMD GCN)

I see a similar behavior on an AMD based system (ThinkPad T14 Gen1).
Comment 3 Michael Catanzaro 2023-03-27 10:33:28 PDT
Hi, this is bug #254117.

*** This bug has been marked as a duplicate of bug 254117 ***