StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
545064
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-02-13T07:34:17.647
FavoriteCount
0
LastActivityDate
2009-02-13T07:34:17.647
LastEditDate
LastEditorUserId
0
OwnerUserId
22656
ParentId
544449
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
The short answer is: unless it has unmanaged resources (file handles etc) you don't need to worry. The long answer is a bit more involved. When .NET decides it wants to free up some memory, it runs the garbage collector. This looks for all the objects which are still in use, and marks them as such. Any local variable (in any stack frame of any thread) which may still be read counts as a root as do static variables. (In fact I believe that static variables are referenced via live Type objects, which are referenced via live AppDomain objects, but for the most part you can regard static variables as roots.) The garbage collector looks at each object referred to by a root, and then finds more "live" references based on the instance variables within those objects. It recurses down, finding and marking more and more objects as "live". Once it's finished this process, it can then look at all the rest of the objects and free them. That's a very broad conceptual picture - but it gets a lot more detailed when you think of the generational model of garbage collection, finalizers, concurrent collection etc. I strongly recommend that you read Jeff Richter's <a href="http://rads.stackoverflow.com/amzn/click/0735621632" rel="noreferrer">CLR via C#</a> which goes into this in a lot of detail. He also has a <a href="http://msdn.microsoft.com/en-us/magazine/bb985010.aspx" rel="noreferrer">two</a> <a href="http://msdn.microsoft.com/en-us/magazine/bb985011.aspx" rel="noreferrer">part</a> article (back from 2000, but still very relevant) if you don't want to buy the book. Of course all this doesn't mean you don't need to worry about memory usage and object lifetimes in .NET. In particular: <ul> <li>Creating objects pointlessly will cost performance. In particular, the garbage collector is fast but not free. Look for simple ways to reduce your memory usage as you code, but micro-optimising before you know you have a problem is also bad.</li> <li>It's possible to "leak" memory by making objects reachable for longer than you intended. Two reasonably common causes of this are static variables and event subscriptions. (An event subscription makes the event handler reachable from the event publisher, but not the other way round.)</li> <li>If you use more memory (in a live, reachable way) than you have available, your app will crash. There's not a lot .NET can do to prevent that!</li> <li>Objects which use non-memory resources typically implement <a href="http://msdn.microsoft.com/en-us/library/system.idisposable.aspx" rel="noreferrer"><code>IDisposable</code></a>. You should call <code>Dispose</code> on them to release those resources when you're finished with the object. Note that this doesn't free the object itself - only the garbage collector can do that. The <code>using</code> statement in C# is the most convenient way of calling <code>Dispose</code> reliably, even in the face of an exception.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow do you get rid of an object in c#
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJon Skeet
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow do you get rid of an object in c#
 singulars
 PostTypePostTypeId
 PTQuestion
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
 VTAcceptedByOriginator
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.