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

show objects size #7

Open
kostya opened this issue Jan 7, 2013 · 1 comment
Open

show objects size #7

kostya opened this issue Jan 7, 2013 · 1 comment

Comments

@kostya
Copy link

kostya commented Jan 7, 2013

Is it possible to add bytesize for each object in the dump?

@Vasfed
Copy link
Owner

Vasfed commented Jan 7, 2013

For most objects this has no meaning because they are allocated in fixed-size slots (size of Rvalue is usually 40 bytes).
Additional c-level heap memory is only allocated for large containers(but they only store references, not the objects), T_DATA(these already have this additional size in dump) and sometimes for tables in instances and classes

So this can be useful only for tracking such cases. I'll consider adding sizes for allocated memory where possible
But because of fragmentation these sizes for most objects do not represent exact memory usage. Actually for determining "priority leaks" you can use string length of dump entries as a metric.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants