cwallen19803
Member
This looks like one for our developer. I added a constraint to an action in several macros. It was slow, I saw this in the log. @MacroDroidDev
As log says, it runs out of memory! We can suppose that some of your macros (maybe the one you're saving but not only) have a great amount of data stored in string variables. As data is saved (global and local as well) along with macros, it can be heavily space consuming.I was only saving changes to macros. This is not action related. It is on the device I've been using for two years. Motorola G Power.
I very well could have been adding waits to the macro when I clicked the save button, but I had added a constraint to an action.
There's a new update 5.26.8 which could fix bugs related to this.If I were running a macro you guys might be right, but I was not.
Neither do any of my macros, when they are running, which they were not, use or store much data. If I have three dozen variables I'd be surprised. None of them is a dictionary.
This occurred,again not while running a macro, but when saving a macro.
No macros were run in the creation of this error.
Thanks for the suggestions anyway. It hasn't reoccurred and I have done nothing to reduce memory use.