High memory usage on asset with lots of JSON GET requests

I have been looking into an issue with my in house dashboard I built and Anthias. Short of the long there is a single asset webpage that makes lots of JSON GET request’s that vary from every 10 seconds to every 15 min depending on the data they return. Hardware is a Pi 4B 8 GB RAM.

I have noticed a slow but steady uptick in memory usage when said asset is displayed until I get the black screen (BlackSOD haha). The web UI remain accessible the whole time.

If I load a simple page such as example .com I do not see this issue and the memory stays steady so I assume it has something to do with all GET’s the page does.

I plan to install Anthias on top of the PI OS this week vs the Balena images so I can grab logs.

For now has anyone seen this issue before and was it an issue in your JS, something with how Anthias does the GC or something else? Maybe I am pushing Anthias beyond it’s limits.

I think my issue is related to these posts:

Are you on the latest release (from master)?

Also, web pages often leak memory. The longer you leave them up, the more likely you are to hit it. A quick workaround is to add an image in the playlist rotation to clear that. Alternatively, you can try the new ‘reload’ feature, but it isn’t as bullet proof.

Yes I am on the 2026.05.0 tagged release.

I have added a image to the rotation so I will monitor. Regardless its not a bad idea so the screen does not get burn in. I did try the reload feature but it did not see to fix it but will reassess.

When looking at the logs on thing I did see, might be my issue but looked odd, was in the anthias viewer logs if you have one asset and the duration is set to 0 it just spams the log to end with updates every second.

Humm the picture does not seem to have worked, up about 15% in a few hours.

As well after disabling the resource memory does not appear to immediately free up.

After a few days the memory still remains unchanged while only displaying a single picture. Any other ideas or should I open up a bug report.

I can confirm this behavior. In my case it’s an online leaderboard that does refresh the score data with JSON.

The memory consumption is slowly creeping upwards. I have added a short video of 26 seconds as an inbetween asset. This slows down the growth of the memory consumption. However it’s not completely gone.

Hmm let me try to see if I can reproduce this. The release we cut today does include some memory optimizations, but let me try anyways.

Thanks for the update. I’ll do my own testing as well to see if I’m still able to recreate it.

So it looks like something’s wrong in the latest release. The pre-built images don’t seem to get past the splash screen and the manual install doesn’t properly pull up the tagged releases.

@venterce just to close the loop on this, I have not seen this issue show up in the new builds.

I tested a few variations of my screen and the memory issues seem to have been corrected in one of the PR’s.

Awesome - thank you for the update.