# High memory usage on asset with lots of JSON GET requests **URL:** \ **Category:** Anthias\ **Created:** [May 19, 2026, 4:53pm UTC](https://forums.screenly.io/t/high-memory-usage-on-asset-with-lots-of-json-get-requests/6692 "2026-05-19T16:53:04Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![mickey](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@mickey](https://forums.screenly.io/u/mickey)\ **Post date:** [May 19, 2026, 4:53pm UTC](https://forums.screenly.io/t/high-memory-usage-on-asset-with-lots-of-json-get-requests/6692/1 "2026-05-19T16:53:04Z")
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: - [Screen going black · Issue #1491 · Screenly/Anthias](https://github.com/Screenly/Anthias/issues/1491) - [White screen and memory leak - Anthias - Anthias Forum](https://forums.screenly.io/t/white-screen-and-memory-leak/1452/4) ---
**Author:** ![vpetersson](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.screenly.io/vpetersson/32/8_2.png) [@vpetersson](https://forums.screenly.io/u/vpetersson)\ **Post date:** [May 21, 2026, 6:01am UTC](https://forums.screenly.io/t/high-memory-usage-on-asset-with-lots-of-json-get-requests/6692/2 "2026-05-21T06:01:18Z")
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. ---
**Author:** ![mickey](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@mickey](https://forums.screenly.io/u/mickey)\ **Post date:** [May 21, 2026, 7:26pm UTC](https://forums.screenly.io/t/high-memory-usage-on-asset-with-lots-of-json-get-requests/6692/3 "2026-05-21T19:26:16Z")
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. ---
**Author:** ![mickey](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@mickey](https://forums.screenly.io/u/mickey)\ **Post date:** [May 21, 2026, 11:51pm UTC](https://forums.screenly.io/t/high-memory-usage-on-asset-with-lots-of-json-get-requests/6692/4 "2026-05-21T23:51:25Z")
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. ![image](https://canada1.discourse-cdn.com/flex029/uploads/screenly/original/1X/5c0b235b8dbd5315b5673ebfda88daa5452bc570.png) ![image](https://canada1.discourse-cdn.com/flex029/uploads/screenly/original/1X/bbe46108fedaffd5ee9d797a5aba4116fc3e0770.png) ---
**Author:** ![mickey](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@mickey](https://forums.screenly.io/u/mickey)\ **Post date:** [May 23, 2026, 11:23pm UTC](https://forums.screenly.io/t/high-memory-usage-on-asset-with-lots-of-json-get-requests/6692/5 "2026-05-23T23:23:52Z")
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. ---
**Author:** ![Whiskydrinker](https://avatars.discourse-cdn.com/v4/letter/w/ac8455/32.png) [@Whiskydrinker](https://forums.screenly.io/u/Whiskydrinker)\ **Post date:** [May 25, 2026, 1:08pm UTC](https://forums.screenly.io/t/high-memory-usage-on-asset-with-lots-of-json-get-requests/6692/6 "2026-05-25T13:08:37Z")
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. ---
**Author:** ![vpetersson](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.screenly.io/vpetersson/32/8_2.png) [@vpetersson](https://forums.screenly.io/u/vpetersson)\ **Post date:** [May 28, 2026, 8:35am UTC](https://forums.screenly.io/t/high-memory-usage-on-asset-with-lots-of-json-get-requests/6692/7 "2026-05-28T08:35:01Z")
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. ---
**Author:** ![mickey](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@mickey](https://forums.screenly.io/u/mickey)\ **Post date:** [May 28, 2026, 12:23pm UTC](https://forums.screenly.io/t/high-memory-usage-on-asset-with-lots-of-json-get-requests/6692/8 "2026-05-28T12:23:02Z")
Thanks for the update. I’ll do my own testing as well to see if I’m still able to recreate it. ---
**Author:** ![mickey](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@mickey](https://forums.screenly.io/u/mickey)\ **Post date:** [May 29, 2026, 12:11pm UTC](https://forums.screenly.io/t/high-memory-usage-on-asset-with-lots-of-json-get-requests/6692/9 "2026-05-29T12:11:34Z")
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. ---
**Author:** ![mickey](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@mickey](https://forums.screenly.io/u/mickey)\ **Post date:** [June 8, 2026, 12:13am UTC](https://forums.screenly.io/t/high-memory-usage-on-asset-with-lots-of-json-get-requests/6692/10 "2026-06-08T00:13:37Z")
@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. ---
**Author:** ![vpetersson](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.screenly.io/vpetersson/32/8_2.png) [@vpetersson](https://forums.screenly.io/u/vpetersson)\ **Post date:** [June 9, 2026, 6:35am UTC](https://forums.screenly.io/t/high-memory-usage-on-asset-with-lots-of-json-get-requests/6692/11 "2026-06-09T06:35:41Z")
Awesome - thank you for the update.