Open the-it opened 3 years ago
This is an interesting one.
We leak memory apparently.
free memory: 320
..........
Active since 1010 seconds
free memory: 160
..........
Active since 1020 seconds
free memory: 155616
..........
Active since 1030 seconds
free memory: 155456
But the garbage collecting than kicks in. My suspicion is that this happens sometimes to late.
Will run some further tests. Use the clock during the day with instrumentation.
Kind of a red herring. I had two breaks today ... both in very healthy memory conditions. :shrug:
I have also had this happen a few times. after a little bit of time it seems to fix itself.
I had this happen with the C code for a while when I first got the device… I ended up trying a different Pico and it hasn't happened since. It could have been the removal and reinsertion, or it could have been a problem with something in the Pico being borderline but other than during a power cut, that one hasn't been off since.
Might be solved by #19
@the-it can you check if, with the new code, you still have issues, mine is now running for month without problem. thx for your feedback.
After running for some minutes, the program crashes and leaves the user with a line of dots (in the shape of one row of the picture to show). Most of the time, this state persists and will not recover. So you have to plug the device out and in again.
Nevertheless, I encountered two times where the clock miraculously returned to the program flow :shrug: .