Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

memory callbacks are not thread safe #147

Closed
RekGRpth opened this issue Nov 25, 2022 · 1 comment
Closed

memory callbacks are not thread safe #147

RekGRpth opened this issue Nov 25, 2022 · 1 comment

Comments

@RekGRpth
Copy link

Since doc https://curl.se/libcurl/c/curl_global_init_mem.html memory callbacks used in curl_global_init_mem must be thread safe, because usually curl is build with threaded resolver.

@pramsey
Copy link
Owner

pramsey commented Dec 5, 2022

Well, curl_global_init_mem is currently disabled, so... and if I recall, were disabled because they were flakey for non-obvious reasons, which tracks. I'm not sure how we'd make them safe, I'm not a threading expert, and not sure if a local semaphor would be useful at all. Since all we're doing is passing the actually calls into the PgSQL mem manager... ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants