Skip to content
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.

/_memusage should dump_rpy_heap before calling objgraph #1028

Closed
pjenvey opened this issue Sep 26, 2017 · 0 comments
Closed

/_memusage should dump_rpy_heap before calling objgraph #1028

pjenvey opened this issue Sep 26, 2017 · 0 comments
Assignees
@pjenvey
Labels
bug Operational p1
Milestone
2017Q3-2.1 Detail...

Comments

@pjenvey
Copy link
Member

pjenvey commented Sep 26, 2017

This makes a lot more sense: objgraph does a fair mount of work introspecting everything. We may have left over garbage from after its run which could potentially pollute dump_rpy_heap's output.
@pjenvey pjenvey self-assigned this Sep 26, 2017
pjenvey added a commit that referenced this issue Sep 27, 2017
@pjenvey
fix: dump_rpy_heap before calling objgraph
dd2b359 
just in case objgraph pollutes its output

Closes #1028
@pjenvey pjenvey mentioned this issue Sep 27, 2017
Merged
pjenvey added a commit that referenced this issue Sep 29, 2017
@pjenvey
fix: dump_rpy_heap before calling objgraph
ece7db1 
just in case objgraph pollutes its output

Closes #1028
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pjenvey pjenvey

Labels
bug Operational p1
Projects
None yet
Milestone
2017Q3-2.1 Detailed heap memory consu...
Development

No branches or pull requests
1 participant
@pjenvey