Created attachment 300549 [details] BT from gdb for epiphany Epiphany 3.22.5 and WebKit 2.15.4. I'm running Epiphany with the dconf key: "process-model" = "shared-secondary-process" And the env variable: "export G_DEBUG=fatal-criticals" The compilation was done with CMake args: '-DENABLE_THREADED_COMPOSITOR=OFF -DPORT=GTK -DCMAKE_BUILD_TYPE=Release -DENABLE_MINIBROWSER=ON -DCMAKE_C_FLAGS_RELEASE="-O0 -g -DNDEBUG -DG_DISABLE_CAST_CHECKS" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g -DNDEBUG -DG_DISABLE_CAST_CHECKS"' After visiting several pages, eventually, the WebProcess hits a Critical. This bug is not reproducible in a predictable way.
(In reply to comment #0) > "export G_DEBUG=fatal-criticals" Obviously, G_DEBUG=fatal-warnings > After visiting several pages, eventually, the WebProcess hits a Critical. Obviously, hits a Warning.
Created attachment 300550 [details] 2nd similar BT from gdb Probably, from the same warning chain. (epiphany:22067): Gtk-WARNING **: Allocating size to GtkSocket 0x5555576b7930 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
This warning also happens with the inspector, that for sure we know how to allocate without calling gtk_widget_get_preferred_width/height(). Same with plugins, we give them the size that the web says they have, not what the widget wants. You can safely ignore this gtk+ warning.
I don't think this report is invalid. We should either fix GTK+ to not warn here, or find a way to work around the warning.
Up to you, I'm not going to spend any time on this.