StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19197494
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-05T11:53:37.027
FavoriteCount
0
LastActivityDate
2013-10-05T12:26:27.520
LastEditDate
2013-10-05T12:26:27.520
LastEditorUserId
2801687
OwnerUserId
2849375
ParentId
10302982
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Sorry to post this as an answer, but I'm new to StackOverflow and don't have enough points to add a comment. Just wanted to add a reference to an issue in the Wonder Github repository that addresses this problem, in hopes it will help lead to a solution: <a href="https://github.com/wocommunity/wonder/issues/130" rel="nofollow">https://github.com/wocommunity/wonder/issues/130</a> -- from user 'nullterminated' (I believe this is Ramsey Gurley, who confirmed the issue -- see <a href="http://comments.gmane.org/gmane.comp.web.webobjects.wonder-disc/19078" rel="nofollow">http://comments.gmane.org/gmane.comp.web.webobjects.wonder-disc/19078</a>) <blockquote> "It appears that ERXObjectStoreCoordinatorPool leaks EODatabase._DatabaseRecord objects whenever the pool size is > 1 and EOs are saved. After many hours in the debugger, I think I understand why..." "Normally, when an EC saves changes, the ObjectsChangedInStore notification is fired, the snapshot is inserted with EODatabase's _fastHashInsert and then the EC refaults the EO when processing changes (updates) or frees the snapshot on finalize (inserts). These actions fire the corresponding _fastHashRemove to free the snapshot." "The problem appears to be that ERXObjectStoreCoordinatorSynchronizer rebroadcasts the ObjectChangedInStore notification to the other OSCs in the pool. This results in snapshots inserted, but with no EC around to clean up, the snapshots are never removed." </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMemory Leak in WebObjects
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMichaC
UserOwnerUserId
1. USNathan
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
 VTApproveEditSuggestion
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.