Page 1 of 1

bug in flow editor

Posted: 08 Jul 2019 15:02
by Rafi4
hi Martin
very strange performance in flow editing place never seen before. I am attaching screen shot.

thanks from record4

Re: bug in flow editor

Posted: 08 Jul 2019 16:29
by Desmanto
What are the floating blue, green, red object at your Screenshot? Do you use Show widget for those?

It seems your phone is running out of RAM, and Automagic doesn't have enough RAM to draw the element. Does it is always happen recently? It seems to be related with your call trigger in your other thread.

Re: bug in flow editor

Posted: 08 Jul 2019 20:01
by Rafi4
hi desmanto
how can I solve the RAM issue? blue, green, red objects? yes exactly overlay widgets. I am discussing about flow elements those were appearing blank in the screen shot.
those blank elements are gone empty after sometime use.

thanks from record4

Re: bug in flow editor

Posted: 09 Jul 2019 17:01
by Desmanto
The blank elements simply not showing up properly on the flow editor, right? If you exit the flow and enter again, or maybe restart your phone, does the flow show up properly?

Unfortunately there is not much you can do, since your phone only has 1 GB RAM. It is very limited for nowadays usage. The best solution is to upgrade your phone and when you do, please at least find minimum 4 GB to ensure Automagic is running properly.

Other small effort you can try is to limit the number apps running and turn off unnecessary flow when you don't need it. It just doesn't worth the effort. The widget that you show maybe consume RAM too when they are being displayed, so you might need to hide them when you don't need them.

Re: bug in flow editor

Posted: 09 Jul 2019 18:15
by Rafi4
hi desmanto
thanks for valuable information.

Re: bug in flow editor

Posted: 11 Jul 2019 19:12
by Martin
Hi,

You can also try to turn on Software rendering in flow editor in Menu->Settings->Workarounds. This could have en effect for such issues and also can reduce the amount of memory used.
Rebooting the device could also help but this would likely be only a temporary fix.

Regards,
Martin