GNOME Bugzilla – Bug 646201
Use the custom main context in SoupProxyResolverDefault
Last modified: 2011-03-30 15:11:41 UTC
Hi, currently the default proxy resolver always uses the default main context. This causes interesting assertions and crashes when using a non-default main context for the async soup session because the non-default main context will be acquired from the main thread, which does not own it. Or even worse, if no main loop is running on the default main context nothing will ever happen. Attached patch fixes this.
Created attachment 184667 [details] [review] Use the custom main context in SoupProxyResolverDefault
Comment on attachment 184667 [details] [review] Use the custom main context in SoupProxyResolverDefault oops. I'll send mail to release-team...
Maybe I should add that this causes problems for GStreamer's HTTP source plugin, which is using a non-default main context and a main loop that runs not in the main thread.
Comment on attachment 184667 [details] [review] Use the custom main context in SoupProxyResolverDefault ok'ed by release-team. http://mail.gnome.org/archives/release-team/2011-March/msg00597.html
commit 87e7ae14487fde5144d16963c4a73612acf0aca5 Author: Sebastian Dröge <sebastian.droege@collabora.co.uk> Date: Wed Mar 30 09:41:33 2011 +0200 Use the custom main context in SoupProxyResolverDefault https://bugzilla.gnome.org/show_bug.cgi?id=646201