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 Pool Tracing #25

Open
michaelquigley opened this issue May 28, 2020 · 0 comments
Open

Memory Pool Tracing #25

michaelquigley opened this issue May 28, 2020 · 0 comments
Milestone

Comments

@michaelquigley
Copy link
Collaborator

michaelquigley commented May 28, 2020

Memory handling trace. Finalization?

https://golang.org/pkg/runtime/#SetFinalizer

Can we augment our memory pool framework to include stack details, allowing us to trace sources of allocations and unrefs?

@michaelquigley michaelquigley created this issue from a note in dilithium Planning (Queued) May 28, 2020
@michaelquigley michaelquigley added this to the v0.2 milestone May 28, 2020
@michaelquigley michaelquigley moved this from Queued to Current Context in dilithium Planning May 28, 2020
michaelquigley added a commit that referenced this issue May 28, 2020
@michaelquigley michaelquigley self-assigned this Jun 9, 2020
@michaelquigley michaelquigley moved this from Current Context to Evaluation in dilithium Planning Jun 12, 2020
@michaelquigley michaelquigley moved this from Evaluation to Backlog in dilithium Planning Jun 12, 2020
@michaelquigley michaelquigley removed their assignment Jun 12, 2020
@michaelquigley michaelquigley modified the milestones: v0.2, v0.3 Jul 22, 2020
@michaelquigley michaelquigley modified the milestones: v0.3, v0.4 Nov 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant