-
Notifications
You must be signed in to change notification settings - Fork 23
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
Allocation tracing #117
base: main
Are you sure you want to change the base?
Allocation tracing #117
Conversation
a64c0c0
to
e6259b5
Compare
This nearly survives compaction, but I think has one more rare-ish bug to work out (I had one failure in 100 runs).
So so keen! Gonna give it a whirl this weekend. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is awesome! Played around with it a bit and everything's working as expected.
TODO: retained profiling mode should be built off of this functionality DONE!
This is a nice win as well.
Should we mention this in the README? Happy to do that in a follow-up.
Co-authored-by: Joshua Young <[email protected]>
I want to add the ability to trace and query allocation information about specific objects in the same way that
ObjectSpace.trace_object_allocations
works, except with full stack information.TODO: retained profiling mode should be built off of this functionalityDONE!