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
I wanted to debug some memory leaks in an application and clicked on the "Active Allocations" header in the Memory window. This made Tracy freeze for several minutes, after which I lost patience and manually killed it (resulting in the loss of the profile).
I suspect that tracy froze because it tried to show a list of 35 million elements, which didn't go so well. In any case, I think I shouldn't be doomed to loose the profile if I click the wrong button, regardless of the number of active allocations. So if this is the reason, I think the list should be automatically clamped to show a manageable number of allocations instead so that Tracy doesn't freeze. Realistically, I don't need to know about all the 35 million allocations anyway, I just need a starting point to fix the leaks, so truncating here would be fine imo.
I am on version 0.10.0, but since I didn't see anything in the changelog regarding this, I believe this might still be an issue in the current version.
The text was updated successfully, but these errors were encountered:
I wanted to debug some memory leaks in an application and clicked on the "Active Allocations" header in the Memory window. This made Tracy freeze for several minutes, after which I lost patience and manually killed it (resulting in the loss of the profile).
I suspect that tracy froze because it tried to show a list of 35 million elements, which didn't go so well. In any case, I think I shouldn't be doomed to loose the profile if I click the wrong button, regardless of the number of active allocations. So if this is the reason, I think the list should be automatically clamped to show a manageable number of allocations instead so that Tracy doesn't freeze. Realistically, I don't need to know about all the 35 million allocations anyway, I just need a starting point to fix the leaks, so truncating here would be fine imo.
I am on version 0.10.0, but since I didn't see anything in the changelog regarding this, I believe this might still be an issue in the current version.
The text was updated successfully, but these errors were encountered: