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
Currently today, all of Objects, Arrays, etc. are all combined within the same constructor within a heap snapshot view. This makes it difficult to get a summary of what types of objects are causing the most memory problem. If instead, we could provide a friendly name to objects, so the aggregation of those events could be based off of friendly name, this would help us in allowing to target the correct objects that will get us the most bang for our buck.
AB#39492569
The text was updated successfully, but these errors were encountered:
This seems like an interesting idea that would, for sure, make it easier to use the snapshot view. I think @zoherghadyali would want to hear about this.
Currently today, all of Objects, Arrays, etc. are all combined within the same constructor within a heap snapshot view. This makes it difficult to get a summary of what types of objects are causing the most memory problem. If instead, we could provide a friendly name to objects, so the aggregation of those events could be based off of friendly name, this would help us in allowing to target the correct objects that will get us the most bang for our buck.
AB#39492569
The text was updated successfully, but these errors were encountered: