StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POAndroid memory leak between activities
primarykey
Id
14620560
data
AcceptedAnswerId
14620698
AnswerCount
5
ClosedDate
CommentCount
9
CommunityOwnedDate
CreationDate
2013-01-31T07:28:29.837
FavoriteCount
0
LastActivityDate
2017-09-06T03:24:36.103
LastEditDate
2013-02-03T21:51:50.633
LastEditorUserId
773737
OwnerUserId
773737
ParentId
0
PostTypeId
1
Score
5
ViewCount
4342
LastEditorDisplayName
text
Body
I'm trying to pinpoint this memory leak. I have two <code>SurfaceViews</code>, <code>A</code> and <code>B</code>. I start <code>A</code>, then navigate to <code>B</code>, then press the back button to go back to <code>A</code>, and then I navigate to <code>B</code> again. I can see my allocated memory rise each time I do this, and eventually I'll get an out of memory error. Here is how I navigate to <code>B</code>, from inside the <code>SurfaceView</code> connected to <code>A</code> <pre><code> Context context = this.getContext(); Intent i =new Intent(context, StartCareer.class); i.addFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP); context.startActivity(i); </code></pre> In both views, I have a lot of Bitmaps drawing. In <code>B</code>, I can't find any references to <code>A</code>, and the only reference outside the context that I can think of is a reference to a Global class that I have. I also have some analytics stuff going on in the background. It could be a million different things, I'd imagine I have the DDMS view on Eclipse up, but I'm not sure what I'm looking at, or how to find the exact object that keeps getting repeated. I'd accept either a crash-course/tutorial on the DDMS Allocation Tracker, or someone to point out what I'm doing wrong. <hr> Additional information: I have some bitmaps being drawn on a <code>SurfaceView</code>. Examples of such from <code>B</code> are: <pre><code>////At class level Bitmap rightB,leftB; ////In the constructor rightB = Bitmap.createScaledBitmap(BitmapFactory.decodeResource(getResources(), R.drawable.right), 100,75, true); ////In doDraw canvas.drawBitmap(rightB, rbX, rbY, null); </code></pre> And my onDestroys <pre><code>@Override public void surfaceDestroyed(SurfaceHolder holder) { if (mThread.isAlive()){ mThread.setMenuRunning(false); } } </code></pre> <hr> So I've run MAT and found one leak, at least. My <code>Thread</code> Keeps getting recreated. Here's what's doing it. <pre><code>@Override public void surfaceCreated(SurfaceHolder holder) { loading=false; if (!mThread.isAlive()){ mThread = new ViewThread(this); mThread.setMenuRunning(true); mThread.start(); } } @Override public void surfaceDestroyed(SurfaceHolder holder) { if (mThread.isAlive()){ mThread.setMenuRunning(false); } } </code></pre> Assuming that these methods get called every time the view loses or gains focus, this seems obviously wrong. How can I re-organize this so that it's not? 
Tags
<android><memory-leaks>
Title
Android memory leak between activities
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USHouseman
UserOwnerUserId
1. USHouseman
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POAndroid memory leak between activities
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POAndroid memory leak between activities
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POAndroid memory leak between activities
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.