Lately we have gotten many reports of heap corruption. This appears to happen when there is a heavy load using http TPC which uses curl. There have been other people reporting curl memory corruption as well, especially when not resetting options upon handle reuse. See curl/curl#4143

The weird thing is that what this bug report talks about seems apparent in the tpc code where XrdTpcTPC.cc:382 is
//curl_easy_setopt(curl, CURLOPT_BUFFERSIZE, 128*1024);

However, not resetting the buffer size may lead curl to corrupt the heap. Why was this line commented out?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1531", "url": "https://github.com/xrootd/xrootd/issues/1531", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1