RAM leak in my Watchface #5033
Replies: 1 comment
-
Posted at 2022-07-26 by @gfwilliams I'm just trying this here and I don't actually see any increase in usage... What if you run If you do just Posted at 2022-07-26 by Hank Thanks for the explanation!
I get this:
So after each status change (1 vs. 2) more RAM is used somehow. When I remove
it seems to stop loosing RAM. So my next guess is one of the widgets. Posted at 2022-07-26 by Hank Very interesting. Deleted the Calendar Week widget. Now it is consistent:
... and then I see this:
D'OH! Posted at 2022-07-26 by @gfwilliams Ahh - is the calendar widget out of date? Posted at 2022-07-26 by Hank Yes, i believe that was the problem. Posted at 2022-07-27 by rigrig Actually... Posted at 2022-07-27 by Hank Oh, wow, good point. Maybe i even mixed them up :) Posted at 2022-07-27 by Hank Lol, the fixed one shows the wrong week 27 while the buggy one shows the correct week 30. Posted at 2022-07-27 by rigrig No, one shows the date, the other the week number. That's why there are two different widgets ;-) Posted at 2022-07-27 by Hank That explains it. Sorry, i'm still in vacation mode. Posted at 2022-07-27 by rigrig Posted at 2022-07-27 by Hank Awesome, thanks! |
Beta Was this translation helpful? Give feedback.
-
Posted at 2022-07-25 by Hank
I am kind of struggeling with RAM issues. The watchface claims low ram after a while. Is there somebody who can check the code for the leak?
https://github.com/espruino/BangleApps/blob/master/apps/hworldclock/app.js
I checked with
So my guess is that the status change from "show every 10 seconds" to "show every second" causes RAM usage. So my theory is that I use and discard the setInterval in a wrong way. Any hints on that?
Beta Was this translation helpful? Give feedback.
All reactions