为什么调用析构函数后 Object 仍在 Memory 快照中

Question

I'm investigating a memory leak and am wondering why after the destructor is called the object Count and Size doesn't change in the memory snapshot. It does look like the Inclusive Size does go down, but not to zero. There are two rows as the first is a view and the second is its view model.

Can anyone explain why this happens? Thank you in advance.

EDIT: I just took another memory snapshot after writing this question up (maybe ~5 minutes later) and it seems the objects are now gone so maybe it just takes some time for everything to go away like longer than a few seconds after the destructor?

Answer 1

Can anyone explain why. . . the destructor is called the object Count and Size doesn't change in the memory snapshot

.NET doesn't have destructors. It has finalizers which are only indirectly related to memory management. An object with a finalizer cannot be garbage collected until after the finalizer is run (or you call GC.SupressFinalize ). But the object is not immediately garbage collected after its finalizer runs.

When GC finds an (otherwise) unreachable object with a finalizer a reference to the object is put on the freachable queue, and the finalizer thread runs the finalizer on all the objects that end up there. The object will be eligible for garbage collection on the next GC run after its finalizer runs. Note that since the object has already survived a GC it will be at least on Gen1. And if it's on Gen2 it may be a while until it's collected.

The decision to reuse C++ destructor syntax for C# finalizers was probably a mistake.