After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 721723 - Soup queue_message behaving different on VMs (blocking) than on Host
Soup queue_message behaving different on VMs (blocking) than on Host
Status: RESOLVED DUPLICATE of bug 707711
Product: libsoup
Classification: Core
Component: Misc
2.44.x
Other Linux
: Normal normal
: ---
Assigned To: libsoup-maint@gnome.bugs
libsoup-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2014-01-07 20:02 UTC by Seif Lotfy
Modified: 2014-01-07 20:20 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
This is what the server does (367 bytes, text/x-python)
2014-01-07 20:02 UTC, Seif Lotfy 		Details
This is what the session does (474 bytes, text/x-python)
2014-01-07 20:03 UTC, Seif Lotfy 		Details

Description Seif Lotfy 2014-01-07 20:02:35 UTC 
Created attachment 265568 [details]
This is what the server does

We have a server and a client.
The server gets a request and hold on to the message (pausing it) for 5 seconds before releasing it again.

The client does a queue_message, which is async. Once it receives a message it queues the message all over again. There is also another glib.timeout_add task that print something every second.

So running this on my system, it works flawlessly. 

On a VM however the session is blocked and the mainloop too. rendering the client useless :(

I will attach minimal code samples to replicate this error.
Comment 1 Seif Lotfy 2014-01-07 20:03:10 UTC 
Created attachment 265569 [details]
This is what the session does
Comment 2 Dan Winship 2014-01-07 20:20:45 UTC 
verified on IRC that this is with 2.42, and fixed in 2.44.1

*** This bug has been marked as a duplicate of bug 707711 ***