StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POMemory allocated when accessing CoreData to-many relationship not released?
primarykey
Id
12183099
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-08-29T17:08:39.013
FavoriteCount
0
LastActivityDate
2012-08-29T18:55:31.103
LastEditDate
LastEditorUserId
0
OwnerUserId
1008770
ParentId
0
PostTypeId
1
Score
1
ViewCount
141
LastEditorDisplayName
text
Body
I'm building a news app where you have a series of images representing the actual articles. When you tap one of them, it opens up the main article page, which has a scroll view on the bottom containing related articles. I found a strange (possibly CoreData related) problem regarding said bottom scroller. When I open the article page, I fetch the related articles, allocate a series of <code>articleViewControllers</code> and add their views to the scroll view. When I switch from the article page, I remove all the views from the scroller and release the <code>articleViewControllers</code>. Upon using Instruments and a couple of heapshots (one before tapping an article and another when switching back to the main page), I found that a substantial amount of memory remains allocated (see images) <img src="https://i.stack.imgur.com/Svq6E.png" alt="enter image description here"> <img src="https://i.stack.imgur.com/KYtqh.png" alt="enter image description here"> When viewing the non-object tab, I discover that most of the allocations happen at the following line of code, in the <code>viewDidLoad</code> method of the above mentioned <code>articleViewController</code>: <pre><code> NSSet *tempSet = [[NSSet alloc] initWithSet:tempArticle.thumb]; //tempArticle.thumb is the actual problem here [tempSet release] </code></pre> <code>tempArticle</code> is an instance of the <code>Article</code> class, a subclass of NSManagedObject. If I comment out these two lines of code, everything works fine, so I'm guessing it's a consequence of faulty CoreData usage. Any help is appreciated. Thanks!
Tags
<ios><core-data><memory-management><one-to-many><nsmanagedobject>
Title
Memory allocated when accessing CoreData to-many relationship not released?
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USDan Cearnau
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POMemory allocated when accessing CoreData to-many relationship not released?
 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.