You are reading a single comment by @Gordon and its replies.
Click here to read the full conversation.
-
I have traced the memory status via console.log. I can't see a huge memory allocation in the code. All memory consuming variables are local with a strict scope and all timer-related ones global, so that there can't be duplicates caused by timers. I meanwhile think that launching the external js is the best solution since it leaves some more memory for new functions :-)
By the way: I got for the first time today a "storage is corrupt" while uploading the app. The firmware handles this in a good way and leaves the device functional although everything must be reinstalled.
Tx
@Gordon
If you're checking via the widget, the widget only updates every minute or so if I recall so you may not be getting an accurate figure?
It's also possible that at some point a function does something that uses a lot of memory for a short while?