I have a self-built Epiphany on 2 machines (latest commit from git that works with GTk3) plus org.gnome.Epiphany.Devel installed through flatpak.
About a week ago at least the 2 self-built versions still worked fine. Now, all launch but display an empty page while the executable consumes >100% CPU, even on internal pages like about:gpu.
The WebKit MiniBrowser application runs normally on both machines (I’m not aware that I have it somewhere in flatpak) so this is not a priori a WebKit issue.
See, the thing is it doesn’t seem logical that 3 different installs of an application, on 2 very different platforms, that all used to work all stop working with the same symptoms all of a sudden. As if I managed to mess up something (like a resource remaining locked after a crash) on 2 different machines. Or 3, if you consider flatpak a kind of VM.
Are you sure it’s not in a crash loop? You don’t have any crashes in coredumpctl?
If the UI process is responsive, then I would attach to the web process with gdb and print a backtrace to see what it’s doing. If the UI process is not responsive, then attach to the UI process.
Well, this is annoying. Issue gone on my Linux machine. The only thing that I did was test if Midori still worked (it did), then recompiled epiphany with -O1 -g and launched it in the debugger. And hop, pages rendered normally again.
This reminds me that when I 1st upgraded webkit (4.1) from 2.40.1 to 2.44.3, epiphany used a lot of CPU on certain sites that warned about missing gstreamer components. Installing gstreamer1-plugins-bad solved that.