StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4375139
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-12-07T09:30:47.810
FavoriteCount
0
LastActivityDate
2010-12-07T09:39:17.297
LastEditDate
2017-05-23T12:11:50.137
LastEditorUserId
-1
OwnerUserId
45664
ParentId
4375064
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Java can only release memory for objects that are no longer referenced (i.e., in use) by the program. And, once an object is no longer referenced, it will be cleaned up fairly quickly (albeit in a way that's out of your direct control). This is likely a straightforward <a href="http://en.wikipedia.org/wiki/Memory_leak" rel="nofollow noreferrer">memory leak</a>. You'll need to analyse the memory to see which objects are there that shouldn't be, and then determine why the garbage collector thinks they are still reachable. At some point in your code you'll be failing to release these variables that are no longer needed (for example, putting them in a <code>Map</code>, though there are many ways of leaking memory if you're not careful). The first step is to analyse the heap to find out which objects are there that shouldn't be. You can use <a href="http://download.oracle.com/javase/6/docs/technotes/tools/share/jhat.html" rel="nofollow noreferrer">jhat</a>, <a href="https://visualvm.dev.java.net/heapdump.html" rel="nofollow noreferrer">jvisualvm</a>, various profilers and likely other tools for this. <hr> The following questions may be of use in solving this issue: <ul> <li><a href="https://stackoverflow.com/questions/40119/how-to-find-a-java-memory-leak">How to find a Java memory leak</a></li> <li><a href="https://stackoverflow.com/questions/670791/common-java-memory-reference-leak-patterns">Common Java memory/reference leak patterns?</a></li> <li><a href="https://stackoverflow.com/questions/2507362/how-to-free-up-memory">How to free up memory?</a></li> <li><a href="https://stackoverflow.com/questions/2960345/best-practice-for-handling-memory-leaks-in-large-java-projects">Best practice for handling memory leaks in large Java projects?</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POjavas memory usage can't release
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USAndrzej Doyle
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POjavas memory usage can't release
 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
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.