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
Unable to start application with Python 3.11.9 + gevent + ddtrace #8903
Comments
Thanks for reporting this, @fbexiga. If turning off the Profiling functionality is an option for your use case, it's the first thing I'd recommend. Does the error still occur when you set |
cc @sanchda |
@fbexiga, thank you so much for the thorough and insightful report. Unfortunately, I don't think we have a short-term workaround, but we'll try to get this resolved promptly. |
That's ok, for now we just downgraded back to 3.11.8. No rush or anything, but I thought it was worth reporting. I tried disabling profiling but still same result. |
I have the same error in a Celery application using Python 3.11.9 + gevent + ddtrace
|
Also affects Python 3.12.3; used to work just fine with 3.12.2. |
Encountered a similar exception, but we don't have profiling enabled. Also happened when moving from
ddtrace==2.7.6 |
There is no clear link between this issue and #8870, but it might be worth testing it once it's released 🤞 . Meanwhile we'll see if we can reproduce this issue |
Was testing this and found that the crash did not happen when we are on an Intel Processor and crashes on AMD EPYC. Disabling Intel processor: Docker image = python:3.11.9-slim
Downgrading to python 3.11.8 stops the crash on AMD EPYC. |
Summary of problem
When trying to start a Flask API using gunicorn + gevent + ddtrace + Python 3.11.9, the application crashes.
However, if I use Python 3.11.8 instead or remove either gevent or ddtrace, it works.
Also, I can only reproduce this issue on a Linux system (like Debian Bookworm), not on MacOS for instance.
Edit: it appears that even after downgrading to Py 3.11.8, with ddtrace 2.7.x the application doesn't start properly, although the error is different. With 2.6.x it does work as expected.
Which version of dd-trace-py are you using?
Tested 2.8.0, 2.7.7 and a few more down to 2.6.3
Which version of pip are you using?
Python 3.11.9 pip 24.0
Which libraries and their versions are you using?
ddtrace==2.7.7
flask==3.0.2
gevent==24.2.1
greenlet==3.0.3
gunicorn==21.2.0
How can we reproduce your problem?
If I try to start a Flask API using gunicorn with gevent workers + ddtrace + Python 3.11.9, i get the following error as soon as the worker boots:
What is the result that you get?
I am unable to start the application, getting the error mentioned above.
What is the result that you expected?
I expected the application to start and work just like it does with an older version of Python.
The text was updated successfully, but these errors were encountered: