mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[PR #763] [MERGED] cleanup curl handles before curl share #1630
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#1630
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/763
Author: @orozery
Created: 5/21/2018
Status: ✅ Merged
Merged: 5/23/2018
Merged by: @ggtakec
Base:
master← Head:cleanup_share_after_handles📝 Commits (1)
af63a42cleanup curl handles before curl share📊 Changes
1 file changed (+2 additions, -2 deletions)
View changed files
📝
src/curl.cpp(+2 -2)📄 Description
Details
I noticed the following warning message repeatedly on my logs:
s3fs.cpp:s3fs_destroy(3438): Could not release curl libraryI debugged it, and found that the reason is a failure in
CURLSHE_OK != curl_share_cleanup(S3fsCurl::hCurlShare)insideS3fsCurl::DestroyShareCurl.The libcurl documentation of curl shares says that you need to:
Currently, s3fs clean up curl handles AFTER the share is destroyed.
This PR fixes this problem, by switching the cleanup of curl handles to be BEFORE the cleanup of the curl share.
I verified that after this fix, the error mentioned above disappears.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.