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.

Sign up for GitHub

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

Jump to bottom

Getting error in profiling, _ProfiledThreadingLock object has no attribute _self_acquired_at #11343

Open
akira opened this issue Nov 10, 2024 · 0 comments
Open

Getting error in profiling, _ProfiledThreadingLock object has no attribute _self_acquired_at #11343

akira opened this issue Nov 10, 2024 · 0 comments
Assignees
@taegyunkim
Labels
Profiling Continous Profling

Comments

@akira
Copy link

akira commented Nov 10, 2024 •
edited
Loading

Upgraded to the most recent release of ddtrace, 2.16.0.

We are now seeing this error on profiling:

Error recording lock release event: '_ProfiledThreadingLock' object has no attribute '_self_acquired_at'

We are seeing these errors, but it also appears to impact the applications as well (queue workers no longer dequeuing tasks). We are using asyncio with uvloop (0.19.0) and Python 3.11.10.
@mabdinur mabdinur added the Profiling Continous Profling label Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@taegyunkim taegyunkim

Labels
Profiling Continous Profling
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@akira @taegyunkim @mabdinur