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 673829 - Race condition between soup_session_abort() and object destruction
Race condition between soup_session_abort() and object destruction
Status: RESOLVED DUPLICATE of bug 673905
Product: libsoup
Classification: Core
Component: HTTP Transport
2.38.x
Other Linux
: Normal major
: ---
Assigned To: libsoup-maint@gnome.bugs
libsoup-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2012-04-10 10:14 UTC by Sebastian Dröge (slomo)
Modified: 2012-04-11 15:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastian Dröge (slomo) 2012-04-10 10:14:07 UTC 
Hi,
when calling soup_session_abort(), immediately followed by g_object_unref() on the session to destroy it, there seems to be a race condition:

+ Trace 230035

  • #0 g_logv
    at /tmp/buildd/glib2.0-2.32.0/./glib/gmessages.c line 765
  • #1 g_log
    at /tmp/buildd/glib2.0-2.32.0/./glib/gmessages.c line 792
  • #2 finalize
    at soup-session.c line 245
  • #3 g_object_unref
    at /tmp/buildd/glib2.0-2.32.0/./gobject/gobject.c line 3018 


There are still message in the message queue of the session, which AFAIU should not be the case after calling soup_session_abort().

This is with 2.38.0 btw
Comment 1 Dan Winship 2012-04-11 13:51:08 UTC 
Are the leftover messages paused? If so, this is bug 673905.
Comment 2 Sebastian Dröge (slomo) 2012-04-11 15:13:06 UTC 
Yes, that's it. Thanks!

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