GNOME Bugzilla – Bug 790894
Do not connect to the session bus when trying GProxyResolverPortal io extension implementation if not under flatpak
Last modified: 2017-11-27 11:38:13 UTC
I've seen crashes like this one in WebKitGTK+ bugs lately:
+ Trace 238192
Thread 1 (Thread 0x7f1ef2ba3f00 (LWP 11083))
This happens at web process startup, when our soup session is created and SOUP_TYPE_PROXY_RESOLVER_DEFAULT is set. It doesn't always happen, and it's not easy to reproduce, so I think the problem is a race condition, maybe related to #674885. I tried to debug it, but without being able to reproduce it, I couldn't figure out what the problem is. What I noticed is that we don't really need to connect to the session bus when we are not under flatpak, so we could at least stop doing so, which will not fix the actual bug, but will fix this crash for sure.
Bugzilla suggested the crash might be a duplicate of bug #781601. I still think it's a good idea to not connect (synchronously) to the session bus when it's not needed.
Created attachment 364488 [details] [review] gproxyresolverportal: do not connect to session bus when not under flatpak
Review of attachment 364488 [details] [review]: Sure.
Comment on attachment 364488 [details] [review] gproxyresolverportal: do not connect to session bus when not under flatpak Pushed https://git.gnome.org/browse/glib/commit/?id=7dcc09e58688ea4c538f77824268a35c9654f5e6