Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App crashing after a few days or a few hours #241

Open
chetstone opened this issue Jul 6, 2023 · 1 comment
Open

App crashing after a few days or a few hours #241

chetstone opened this issue Jul 6, 2023 · 1 comment

Comments

@chetstone
Copy link
Contributor

After a period of time, the app stops and displays a LogBox error message:

Uncaught Error
Property storage exceeds 196607 properties

Usually the display indicates the message has been repeated many times. The only way to recover is to kill the app and restart.

Smartphone (please complete the following information):

  • Device: [Android SM-T500]
  • OS: [Android 12]
  • ColdChain Version [v0.5.3-rc5 merged with my fahrenheit display changes]
    Screenshot_20230703-234222_mSupply ColdChain
    Screenshot_20230701-100840_mSupply ColdChain

Additional context
Seems to be happening more often. When I first started this test, about a month ago, things ran for a couple of weeks before this happened. Lately, it happens after a few hours.

I guess this means the sqlite database is full? It may be because I'm using the app in a way that is a bit different from most MSupply customers: I am monitoring 4 sensors with 5 minute update, and I have no connection to an upstream database. I have tried browsing the sqlite file on my computer. It currently contains about 28K data points, starting from about three hours ago, when I most recently restarted the app. So apparently the DB gets reset when the app is restarted. Yet is very large: 11 MB-- go figure. And it seems to be recording 7 entries every minute, even though my update interval is set to 5 minutes.

Is there some setup that I might be missing?

thanks

Chester

@mark-prins
Copy link
Contributor

mark-prins commented Dec 5, 2023

have just had exactly the same issue!
this is running a build which includes the fix for #270

and a hint with this issue
a map could be helpful as per this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants