Slooooow memory leak somewhere?

Hello,

Not sure if this post best fit here or on the github, but I noticed something lately.

I am not really somebody that use the watch for other things that the time and light up the screen when needed. And when I am at home I do not even wear it so it often stay week without being used much. On that not the battery lifespan is awesome, with my usage I often reach a full month without having to charge it!

Back to the problem, my default screen is running with the Anton Clock and the widgets lock, bluetooth and battery level (vertical). All up to date and in attachement.

I noticed that after a few days wihout use, if I try to connect to the watch to see if there are update available, it generaly fail to connect until I reload the screen on the Banglejs. often, but not all the time before I do that reload there is displayed at the bottom on the screen "memory busy", I would join a photo if that was currently the case but no "luck" this time, maybe in a few days if an update is asked.

My guess is that one of the 3 widgets or the clock is slowly eating memory while running, or just something in the firmware? I am not sure since I do not have the level of knowledge needed to understand the code of all of them. But maybe talking about it may point one of you in the direction?

1 Attachment

• Banglejs backup.zip

Hi,

it generaly fail to connect until I reload the screen on the Banglejs.

When you say reload, do you mean with a reasonably short press of the button (~2 seconds), or a full reboot (~10 seconds, that shows the blocky bootloader text)?

I've come across the MEMORY_BUSY error here sometimes too. In 2v15 and later it should happen a lot less often, but it does seem it can still occur. It's frustrating, but it is more of a warning and isn't a sign that memory is 'leaking'. It shouldn't affect the stability of the Bangle at all, so it's a bit odd about your issues connecting...

Hello,

Most of the time just the short press is enough to bring back to work everything. I maybe have to do a full reboot one out of ten time if the bluetooth still does not respond after.

It shouldn't affect the stability of the Bangle at all

Even if it was displayed it does not affect anything into the Bangle, I can still open the settings or any applications without any issue and it disapear until the next time.

so it's a bit odd about your issues connecting...

I would love to help more, I admit my usage of the Bangle is more of a wall clock most of the time and I almost never switch from the clock itself, with that and the message I imagined both could be linked.

For the state of today:
I did not touch it since my post 3 days ago, no MEMORY_BUSY message, I tried going to the espruino.github.io page to connect to the Bangle (from Chrome, up to date). It connect, the bluetooth widget become blue, and in the end the application fail at getting the app list.

I tried two more times to be sure then while writting this post I remembered that the main site for the application was directly on banglejs.com and tried connecting from there instead and that worked directly. Got back to the github page version and that worked well too. That make me a little more confused since both site are relatively the same if I recall?

But it seem that everything on the Bangle side seem to work well, maybe the fail at the app list collection was what made me think that.

That make me a little more confused since both site are relatively the same if I recall?

They should be pretty much, yes.

What firmware version do you have on your Bangle sat the moment?

Maybe next time, please could you try connecting with the Web IDE (https://www.espruino.com/ide/) and see if that shows up any error messages in the console? It might be it gives some clue what's going on.

Also, it's always worth disabling and re-enabling Bluetooth on your PC. It's always surprising to me just how often the host computers seem to have issues with the Bluetooth adaptor.

I am running the firmware 2v15

I tried the github page version just now, it connected directly, I had an update for the calendar app, so I applied it, disconnected, then opened the IDE and tried to connect and just got the message "Connection Failed."

Because of the update the Bangle was on the "hold button to reload" screen, so I did it and retried connection. Same "Connection Failed." Result.

Then tried to disable/enable the bluetooth on the computer (Win 10 pro, up to date, Intel Wireless-AC 9560 integrated chip for wifi/bt 5.1), and it finally connected.

I will try again and update this post the next time the connection to github page/app store fail.

A late update after already 2 month and the new firmware update.

I never saw the MEMORY_BUSY message since then, and for the connection same thing, it may have happened only once or twice for 12 ish connections.

I assume that 2v15 fixed a lot of what was happening from the start, that it did not reappear in 2v16, and that the main culprit for the connection is only windows and the bluetooth drivers.

Thanks for all your work! ❤

That's great - thanks for the update, and glad it's all working better now!