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
'cannot allocate memory in static TLS block' error got after bump to version 2.7.1 #8616
Comments
Thanks for the report, @Surgo. The diff between 2.7.0 and 2.7.1 is pretty small and only contains commits from two authors, @romainkomorndatadog and @gnufede, though nothing immediately jumps out to me as an obvious cause of this behavior. |
My only commit for this release is 3363812 so think I'm going to, respectfully, bow out. That said, this looks very similar to actions/runner-images#4733 . I don't know if our build artifacts ended up with a different extension/binary/something. That may be a more likely culprit than actual commit changes. |
👋 Hi @Surgo! Thank you for the report and the analysis. Some details (these may or may not be widely known) for completeness. This error comes from ld.so when it is unable to accommodate the static TLS requirements of a dynamically-loaded library (e.g., one opened via One common resolution is to use the To begin, what I'll need is a log of These examples pipe stderr to a file in
If you'd prefer not to share these files publicly, please file a ticket with Datadog support. They'll provide a means to share private information with us. If you'd like, I can also DM you my Datadog contact information. In the meantime, I'll try to do some analysis of this defect with the information I have. Many thanks! |
@Surgo, I did some more analysis on this side. Please do not waste your time with the analysis I requested. I think we may be able to improve the library without any additional context. |
The results are as following: /tmp/ld_2.7.0.log
|
🙇 Thank you very much, @Surgo ! I'll review these results to make sure they're consistent with our understanding of the problem. |
Summary of problem
After upgrading to version 2.7.1, I can no longer import
MySQLdb
via Django'smanage.py
(alsocelery
) viaddtrace-run
.Which version of dd-trace-py are you using?
2.7.1
Which version of pip are you using?
24.0
Which libraries and their versions are you using?
`pip freeze | grep -iE 'ddtrace|mysql'`
How can we reproduce your problem?
What is the result that you get?
What is the result that you expected?
Import libraries that using Python/C API
2.7.0
works fine for meThe text was updated successfully, but these errors were encountered: