On Thu, Nov 13, 2025 at 01:21:56PM +0100, Emilio Pozuelo Monfort wrote: > On 12/11/2025 08:13, Sylvain Beucler wrote: > > Hi, > > > > On 10/31/25 13:48, Emilio Pozuelo Monfort wrote: > > > On 31/10/2025 13:16, Adrian Bunk wrote: > > > > On Fri, Oct 31, 2025 at 11:05:46AM +0100, Emilio Pozuelo Monfort wrote: > > > > > On 02/09/2025 11:51, Adrian Bunk wrote: > > > > > > On Fri, Aug 29, 2025 at 01:30:05AM +0300, Konstantin Pokotilenko > > > > > > wrote: > > > > > > > В Чт, 28/08/2025 в 12:59 +0300, Adrian Bunk пишет: > > > > > > > > On Wed, Aug 27, 2025 at 10:08:05PM +0300, Konstantin Pokotilenko > > > > > > > > wrote: > > > > > > > > > В Ср, 27/08/2025 в 20:30 +0300, Adrian Bunk пишет: > > > > > > > > > ... > > > > > > > > > > Two additional questions: > > > > > > > > > > 1. Do you have an HTTP proxy configured? > > > > > > > > > > 2. If yes, using PAC (proxy auto-config)? > > > > > > > > > > > > > > > > > > > > I am asking since my guess is that the new WebKitGTK broke > > > > > > > > > > libproxy1-plugin-webkit, which is used for parsing PAC > > > > > > > > > > files. > > > > > > > > > > > > > > > > > > Thanks for quick response. > > > > > > > > > > > > > > > > > > No HTTP proxy used. > > > > > > > > > > > > > > > > > > I found out a simpler reproduction, it is to just run WebKit > > > > > > > > > example > > > > > > > > > browser: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/MiniBrowser > > > > > > > > > ... > > > > > > > > > > > > > > > > That was helpful. > > > > > > > > > > > > > > > > Please check if you have libproxy1-plugin-networkmanager > > > > > > > > installed, and whether removing it fixes the issue. > > > > > > > > > > > > > > It was installed. Removing it fixes the issue. > > > > > > > > > > > > Emilio, I can reproduce this in bookworm by compiling webkit2gtk > > > > > > with > > > > > > libc++-16 there. > > > > > > > > > > Were you able to reproduce this on bullseye? > > > > > > > > Yes: > > > > > > > > $ /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/MiniBrowser > > > > WebKitNetworkProcess: /build/libproxy-cqqv9A/libproxy-0.4.17/ > > > > libmodman/module_manager.hpp:58: std::vector<T*> > > > > libmodman::module_manager::get_extensions() const [with T = > > > > libproxy::network_extension]: Assertion `obj != NULL' failed. > > > > ERROR: WebKit encountered an internal error. This is a WebKit bug. > > > > ../Source/WebKit/WebProcess/Network/WebLoaderStrategy.cpp(577) : > > > > internallyFailedLoadTimerFired > > > > > > > > > I am trying to, by installing > > > > > libproxy1-plugin-networkmanager, setting a proxy in NM (via PAC file > > > > > or URL), > > > > > > > > No proxy setting required. > > > > > > > > > but I can't get MiniBrowser to crash. > > > > > > > > MiniBrowser itself does not crash. > > > > > > > > Does it show you a webpage or "WebKit encountered an internal error"? > > > > > > With no proxy set, it shows me webkitgtk.org, and I can navigate just > > > fine (e.g. go to the planet.webkitgtk.org link, or enter https:// > > > google.com). > > > > Same here. > > > > Also for the previous atril report #1101807, my base bullseye VM has > > libproxy1-plugin-networkmanager installed as a dependency of package > > 'gnome', so it already was installed when I attempted to reproduce the > > issue there. > > > > Hence some additional condition seems required to trigger the issue. > > I have prepared a backport of webkit 2.50.1 to bullseye. Adrian, can you try > it out and see if that still crashes? Or if you have any further input on > how to reproduce the crash I'd try with 2.48 (and then with 2.50). Binaries > are available from [1].
Still reproduces for me. One thing I noticed is that the crash in MiniBrowser does not happen in 100% of all cases, the problem might be some corruption that manifests in different ways. I am always getting the ERROR: WebKit encountered an internal error. This is a WebKit bug. in the terminal where I started MiniBrowser. > Cheers, > Emilio cu Adrian
