StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
30227
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-08-27T14:12:23.633
FavoriteCount
0
LastActivityDate
2016-01-19T10:25:19.310
LastEditDate
2016-01-19T10:25:19.310
LastEditorUserId
3305116
OwnerUserId
3237
ParentId
104
PostTypeId
2
Score
15
ViewCount
0
LastEditorDisplayName
text
Body
The best explanation of how the garbage collector works is in Jeff Richters <a href="https://www.microsoftpressstore.com/store/clr-via-c-sharp-9780735667457" rel="noreferrer">CLR via C#</a> book, (Ch. 20). Reading this gives a great grounding for understanding how objects persist. One of the most common causes of rooting objects accidentally is by hooking up events outisde a class. If you hook up an external event e.g. <pre><code>SomeExternalClass.Changed += new EventHandler(HandleIt); </code></pre> and forget to unhook to it when you dispose, then SomeExternalClass has a ref to your class. As mentioned above, the <a href="http://memprofiler.com" rel="noreferrer">SciTech memory profiler</a> is excellent at showing you roots of objects you suspect are leaking. But there is also a very quick way to check a particular type is just use WnDBG (you can even use this in the VS.NET immediate window while attached): <pre><code>.loadby sos mscorwks !dumpheap -stat -type <TypeName> </code></pre> Now do something that you think will dispose the objects of that type (e.g. close a window). It's handy here to have a debug button somewhere that will run <code>System.GC.Collect()</code> a couple of times. Then run <code>!dumpheap -stat -type <TypeName></code> again. If the number didn't go down, or didn't go down as much as you expect, then you have a basis for further investigation. (I got this tip from a seminar given by <a href="http://www.thinktecture.com/staff/ingo" rel="noreferrer">Ingo Rammer</a>).
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAnatomy of a "Memory Leak"
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USGus Paul
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.