memory leak after update ?

[i8890321]

I am using tasker 4.0
I find that the memory usage (ram) is abnormally high, it goes to 12x mb. I never have this before . Anyone having the same thing ?
to clarify one point is no profile is activated and only one scene shown(I call it sidebar)
Should I re instaall it ? I just update it from the beta version.

[UncleMike]

I've been experiencing a memory leak since before b16.  I've got 100+ profiles, but the leak only seems to occur with UI usage.  Without opening the UI, memory usage stays around 25MB, but with significant UI usage I've seen it climb to over 90MB.  I have yet to identify any specific UI elements whose use results in a leak.

Rebooting the device clears the problem temporarily, as does killing the monitor process, but both of these require that the device is rooted.

[Cptnodegard]

Same here. After a clean reboot, Tasker uses about 15MB. Even though every scene is properly destroyed, and everything is otherwise identical, it starts climbing above the 50s and 60s after some use. 

[Pent]

> I've been experiencing a memory leak since before b16.  I've got 100+
> profiles, but the leak only seems to occur with UI usage.  Without opening
> the UI, memory usage stays around 25MB, but with significant UI usage I've
> seen it climb to over 90MB.  I have yet to identify any specific UI
> elements whose use results in a leak.
>
> Rebooting the device clears the problem temporarily, as does killing the
> monitor process, but both of these require that the device is rooted.

Does simply turning off Tasker then exiting the UI have any effect ?

Pent

[Cptnodegard]

None whatsoever, and I can't even force close it, I assume due to it having device admin access

[TaskerAholic]

It is old issue to me...

If I play with scenes for about 10 min. or something, it gets out of memory.

No any help to turn Tasker off and on but have to reboot for another 10 min... : - (

BR

2013년 4월 4일 목요일 오후 12시 5분 36초 UTC+9, i8890321 님의 말:

[UncleMike]

No.  Disabling and re-enabling Tasker has no effect on the memory usage.

[Erez Dasa]

The same problem here.

downgrade to the blue & works version.

[Cptnodegard]

Generally speaking I've noticed Tasker becoming a lot slower since the UI update. Sometimes I hit the back button to get out of something and I can essentially make dinner by the time it decides to do as it's told. 

[Pent]

> No.  Disabling and re-enabling Tasker has no effect on the memory usage.

Is that disabling and exiting UI via Back ?

How about if you swipe away from Recent Apps after exiting ?

Pent

[Cptnodegard]

Only thing that works for me is finding an app that doesn't mind killing a "system app", which is what Tasker appears as with device admin active. Got it down from 37 to 20MB of RAM use now by doing that. Disabling, exiting via UI, and removing from recent apps does nothing for me

[Pent]

It occurs to me that probably everyone posting here has a lot of data
defined.

Maybe copies of the data are not being reclaimed.

Could someone try backing up data, then deleting it all, then reboot.
Does going back into Tasker and messing around with scenes, tasks etc
for a bit, then exiting, cause the memory loss still ?

Pent

[UncleMike]

On Sunday, April 14, 2013 3:16:08 AM UTC-4, Pent wrote:

> No.  Disabling and re-enabling Tasker has no effect on the memory usage.

Is that disabling and exiting UI via Back ?

Yes, I was referring to disabling Tasker in the UI, the pressing Back to exit the UI.

 

How about if you swipe away from Recent Apps after exiting ?

I haven't opened the UI all day (since a battery pull 15 hours ago) and Tasker is happily sitting at 22MB.  After a little UI activity I got it up to 35MB.  Swiping away after exiting, brought it down to 20MB.  But 3 subsequent attempts produced no noticeable difference after swiping.

[UncleMike]

I'll give it a shot, but it will be several hours before I can do it.  I'll let you know how it goes.

For the purpose of confirming (or not) your suspicion, I'll say that I have 111 profiles defined - most of which are enabled.  I'll let you decide if that qualifies as a lot.

[Pent]

> I'll give it a shot, but it will be several hours before I can do it.  I'll
> let you know how it goes.

Thanks!

> For the purpose of confirming (or not) your suspicion, I'll say that I have
> 111 profiles defined - most of which are enabled.  I'll let you decide if
> that qualifies as a lot.

Don't think there's a subjective opinion needed for that :-)

Pent

[Pent]

Guys, another couple of test cases:

- go into the main screen profile list than exit without doing
anything a few times, then exit with back
- go into the main screen profile list, toggle a profile enabled
status (to force data save) then exit a few times

(starting from the no-problem memory level in both cases)

Thanks,

Pent

[Pent]

Sorry, one more: how about if Tasker is disabled ? Does messing around
in the UI and exiting a few times produce bloat ?

Pent

[Cptnodegard]

About to run out the door so don't have time to test any of this right now, but just thought I'd add in that I do have a lot of crap defined. Not sure how many profiles/tasks/scenes are still around, but the userbackup file is 19300 lines

[Cptnodegard]

-  go into the main screen profile list than exit without doing
anything a few times, then exit with back

raised RAM use 6MB by doing this 5 times 

 

-  go into the main screen profile list, toggle a profile enabled
status (to force data save) then exit a few times

Starting at the above scenario, lost another 4MB by doing this once

That landed me at 27MB, which is still nothing compared to 50-60MB RAM use before Tasker simply says "kthx byebye" and crashes. Scene editor seems to strangle the poor thing the most 

[Wietse van Buitenen]

I'm also experiencing FC's when batch changing stuff in the UI and then close with the Back button.

After a crash it goes fine for about 4 or 5 closes and then the next time a crash occurs and the last modifications are lost.

I try to save every few changes so I don't lose to much.

No crash occurs when not opening the UI.

I'm a bit short on time this week but I'll try to test the cases Pent mentioned and give some feedback..

[Pent]

> I'm also experiencing FC's when batch changing stuff in the UI and then
> close with the Back button.

I've fixed a few of those that occured when the app is short of
memory. If it's still happening
after u2 could you send me a log ?

Also, please wait for u2 for memory testing to see if the changes I've
made have helped.

Thanks,

Pent

[Pent]

> But I've been checking my battery life (not because of tasker) and I've
> seen a lot of garbage collection. In sleep mode (last night), with no tasks
> running and almost all profiles disabled, I've seen like fifty lines (one
> each ten minutes) like this in logcat:
> 04-16 23:35:09.160 D/dalvikvm( 2512): GC_CONCURRENT freed 1910K, 54% free
> 6468K/14023K, paused 2ms+4ms
>
> Process 2512 was net.dinglisch.android.taskerm, so it suggests a memory
> leak in the monitor?

If you've got e.g. a location profile or time context that goes every
10 minutes, that's probably it (freeing up temp memory that was used
for the background checks)

Pent

[Cptnodegard]

No joy on latest beta. 56MB after being in and out of scene edits for the sake of an article, a reboot later and down to 15MB. Become standard procedure to have to reboot the phone whenever I've written a Tasker post xD

[Pent]

> No joy on latest beta. 56MB after being in and out of scene edits for the
> sake of an article, a reboot later and down to 15MB. Become standard
> procedure to have to reboot the phone whenever I've written a Tasker post xD

I didn't change anything with the scene editor yet, but I was hoping
the 'just go in and
out of Tasker' leakage would be helped ? If so, I will take similar
steps with the other
screens.

Pent

[Wietse van Buitenen]

worth mentioning is that the things I'm editing now are also mostly related to Scenes (JS in buttons and images) when I experience the crashes..

[Cptnodegard]

It seems to increase a few MB when I enter and leave the app a few times, but then it lowers back down again after I've been out for a while. 

On Friday, April 19, 2013 8:38:06 AM UTC+2, Pent wrote:

[TaskerAholic]

Dear Pent,

I experienced this problem(crash after using scene edit) last version not on the latest version.  

This happen after excessive use of scene edit and once this happen, you should remove and re-install Tasker not to repeat(no meaning to reboot), 

and have to care(?) or limit your scene editing not to make it again.    

Thanks

[Pent]

> It seems to increase a few MB when I enter and leave the app a few times,
> but then it lowers back down again after I've been out for a while.

That's as it should be.

Pent

[UncleMike]

My experience with the memory leak doesn't involve scene editing at all - just profiles and tasks, plus the necessary scrolling that goes with it.

[Pent]

> My experience with the memory leak doesn't involve scene editing at all -
> just profiles and tasks, plus the necessary scrolling that goes with it.

UM, if there's nothing private in there, maybe you could ship me your
userbackup.xml for testing ?

Pent

[UncleMike]

The only thing private is in the Secure Settings configuration for some actions, which is encrypted anyway.  I wouldn't post it publicly, but I'll ship it off to you.  FYI - I have let Tasker go over 24 hours with no UI use (it's hard to go cold turkey), and memory never climbed, so I don't think the leak has to do with the functional contents of the profiles, though it may have something to do with displaying their contents, or certain actions.  When the leak really became problematic I was working on a calendar-related profile that uses the Test action, and scrolling the list of available things to test frequently, which became VERY sluggish.

The backup will be on its way soon.

[Pent]

> The backup will be on its way soon.

Thanks.

I spent 20 minutes scrolling around, editing, in and out of scenes etc
(and leaving and entering the app sometimes) and looking at the memory
usage in the 'Running Apps' part of Android Settings. It usually
hovered around 28MB. I could get it up to 30MB sometimes but then when
I ran a few other apps it would drop back to the 27-29 range.

This was on 4.1.2 BTW.

Not sure where to go from here, it's not practically feasable to try
and fix stuff I can't reproduce.

Pent

[Bob Hansen]

I have experienced Tasker using 80+ Megabytes of ram. At which point the phone is slow and I ultimately need to power off the phone and power on to get things going again. This happens when I am experimenting with creating/modifying profiles and tasks (scenes need not be involved but it does occur more quickly when they are).

I have a Droid RAZR HD (XT-926); stock rom 4.1.2; rooted and Tasker 4.0u2.

I am willing to try to work on this if it would be useful to you. 

Obviously, you want a reproducible sequence that causes the problem. 

What additional information, logs, etc. would be useful to you to aid you in reproducing a problem like this?

I do have experience in working with developers on debugging software. I was a quality control engineer specializing in software quality before I retired.  

[Pent]

> I just bought this app yesterday. woke this morning to find tasker using
> 92MB. Ridiculous. Restarted app, it was down to 15MB.

Presumably you only have very few things configured, which differs
from everyone else on this thread (who I believe all have a lot of
data defined)

Could you do Menu / Data / Backup and send me userbackup.xml from the
Tasker dir on SD ?

Thanks,

Pent

[Pent]

Making some progress on UI memory usage, hang in there.

Pent

[UncleMike]

FYI - I created a task that uses several Test actions, and memory use skyrocketed to almost 100MB.

[Pent]

> FYI - I created a task that uses several Test actions, and memory use
> skyrocketed to almost 100MB.

Impressive :-)

Which test types ?

Pent

[UncleMike]

Almost all of the Calendar related ones: Calendar, Title, Start, End, Available.

When I first noticed the problem during beta, I was also working calendar related test actions.

[Juan González]

so had the developer acknowledged the bug?

[Pent]

so had the developer acknowledged the bug?

I spent a lot of time minimizing UI and other RAM usage in response to this.

Pent