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 452280 - Data corruption when using soup_message_io_pause() from a "got-chunk" callback
Data corruption when using soup_message_io_pause() from a "got-chunk" callback
Status: RESOLVED FIXED
Product: libsoup
Classification: Core
Component: API
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Dan Winship
Dan Winship
Depends on:
Blocks:
 
 
Reported: 2007-06-29 15:17 UTC by Marco Barisione
Modified: 2007-11-19 17:56 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
An example (2.81 KB, application/octet-stream)
2007-06-29 15:18 UTC, Marco Barisione 		Details

Description Marco Barisione 2007-06-29 15:17:33 UTC 
If soup_message_io_pause() is called from the "got-chunk" callback then the callback is called with junk in msg->response.body.
Comment 1 Marco Barisione 2007-06-29 15:18:13 UTC 
Created attachment 90883 [details]
An example
Comment 2 Dan Winship 2007-10-28 17:26:28 UTC 
Oops, sorry about the delay. I sat down to debug this and then realized that
the answer is "don't do that then". soup_message_io_pause() is only for
server-side message processing. I've clarified the docs to indicate that.
Comment 3 Dan Winship 2007-11-14 20:29:02 UTC 
OK, someone else wants this functionality too...
Comment 4 Marco Barisione 2007-11-19 13:37:19 UTC 
Without this fix is not possible to do async I/O when receiving a file.

I use libsoup in telepathy-salut to send/receive files in a LAN, so the network could be faster than the disk and I have to choose between doing sync I/O (freezing the process!) or buffering everything in memory. Please fix this bug :)
Comment 5 Dan Winship 2007-11-19 17:56:42 UTC 
fixed in CVS, and will go out in libsoup 2.2.104 with GNOME 2.20.2 next week