You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Is it possible to add bytesize for each object in the dump?
The text was updated successfully, but these errors were encountered: