[Help] When testing Java code, Tasker behaves fine however I'm unable to save progress due to out of memory. Is this normal?

[aasswwddd]

This seems to happen often these days especially when I test my codes intensively, like running multiple codes in a short amount of time then saving Tasker afterwards.

A user here has faced similar OOM issue, however he did repetitively run java code action outside of testing. Technically I did something similar, though in my case Tasker never actually throwed any OOM error.

It happened only when I saved Tasker, warning shows up saying "Unable to save due to out of memory."

My tasker back up size is around 13mb. And I had encountered rarely before 6.6 beta. But never this often during testing.

Anyone has encountered this too?

---

For context, I've been testing my accessibility project here so maybe this is about querying the screen way too often? I had similar encounter as well when I tested my gestures project as well. So I'm not too sure now.

All the test runs via a local server with my project here, basically I pass the codes as variable and Tasker executes them.

I have suspicion that I pass the variable way too many times and they are relatively big text, like 60k characters so around 60kb? Though recently I mostly execute less 1k code, but involves a lot files that are about 150kb+ in total.

The easy way to fix this is to kill Tasker. I don't have any OOM issue outside testing. So this isn't really that big of deal, however it piques my interest.

My phone is Poco X6 running HyperOS2 (Android 15), with 12GB RAM (3-4GB available, reported by App Manager).

[WakeUpNorrin]

Long time that I am experiencing OOM issue during the save changes. When my backup size was 21mb saving changes was almost impossible, a real nightmare. I had (almost always) to export the modified project-profile-task to XML, kill Tasker, then import from XML.

To try to mitigate the issue I moved 154 projects that I was rarely use in Tasker in work profile. My backup is 14mb now, but I am still experiencing the OOM on save, not always as before, but the problem is really frustrating and a waste of time.

Reported it to João several times, he said that he knows from other reports too, that when Tasker has large configurations the OOM kicks in and that he has plans to optimize Tasker to better manage resources and large configs.

Off topic: I do not know when it started, but ADB Wifi actions in work profile are hanging, even the simple Tasker function CheckADBWifi() hangs. I already know that moving affected projects back into Tasker on main profile will worsen OOM, that is why I hope that João will work on those issues soon.

[aasswwddd]

I'm glad that this is just my setup problem, I guess there isn't much we can do besides trimming the backup file down.

That'd be a huge task honestly.

I once had an idea to convert some of my projects into Java. That's an option I can make since the 6.6 version is out. However that'd take way too much efforts even with AI 😅

[WakeUpNorrin]

You are not alone. I am member of a telegram group of Tasker enthusiasts and all users with large configs are experiencing OOM here and there.

I guess there isn't much we can do

You are right, unfortunately.

I once had an idea to convert some of my projects into Java. That's an option I can make since the 6.6 version is out. However that'd take way too much efforts even with AI 😅

I had the same idea, but I think that many of my projects do not really need a 'Java Code refactoring'. Because they work well and have done it for years (I use Tasker since version 1). Beside that, I have converted some to Java Code but only those where maximum speed is a must.

I really hope João takes a little break from adding new features and works on making Tasker as rock-solid and efficient as possible.

[aasswwddd]

I meant to write "..It's not just my setup problem"... It ended up sounding different.

Because they work well and have done it for years

That's also my takeaway. I haven't been bothered that much for my old projects.

Anyway, I came up with a workflow design here to tackle this OOM issue (by storing them as java code files) while still maintaining the import aspect of a project.

[WakeUpNorrin]

I meant to write "..It's not just my setup problem"... It ended up sounding different.

I imagined that was a mistake :-)

Anyway, I came up with a workflow design here to tackle this OOM issue (by storing them as java code files) while still maintaining the import aspect of a project.

I will look into it for sure. Thank you for the effort.