[GH-ISSUE #444] Low on memory. Fallback to 8bpp #2479

Closed
opened 2026-03-20 21:06:56 +01:00 by sascha_hemi · 5 comments
Owner

Originally created by @gitpower2017 on GitHub (Feb 28, 2025).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/444

I have recently received this error message in the LOG.

16:02:29 File has size 0. /temp/FFFFFFFF1C01DC00.raw
16:02:28 low on memory. Fallback to 8bpp
16:02:28 Updating FFFFFFFFFF1C01DC00

The TAG does not accept any updates and the display is always the same. I have sent less information via JSON as a test. same result.

Other tags are also affected.
Do I have to rewrite the file system on the ESP32?

The json string:

"mac=FFFFFFFF1C01DC00&json=[{"box": [1,21,169,3,3]},{"text":[5,0, "Müllkalender", "fonts/calibrib30", 1] },{"text":[2,30, "Graue Tonne", "fonts/calibrib30",1] },{"text":[171,30, "Heute", "fonts/bahnschrift30",1] },{"text":[2,55, "Gelber Sack", "fonts/calibrib30",1] },{"text":[171,55, "In 5 Tagen", "fonts/bahnschrift30",1] }]"

Originally created by @gitpower2017 on GitHub (Feb 28, 2025). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/444 I have recently received this error message in the LOG. 16:02:29 File has size 0. /temp/FFFFFFFF1C01DC00.raw 16:02:28 low on memory. Fallback to 8bpp 16:02:28 Updating FFFFFFFFFF1C01DC00 The TAG does not accept any updates and the display is always the same. I have sent less information via JSON as a test. same result. Other tags are also affected. Do I have to rewrite the file system on the ESP32? The json string: "mac=FFFFFFFF1C01DC00&json=[{"box": [1,21,169,3,3]},{"text":[5,0, "Müllkalender", "fonts/calibrib30", 1] },{"text":[2,30, "Graue Tonne", "fonts/calibrib30",1] },{"text":[171,30, "Heute", "fonts/bahnschrift30",1] },{"text":[2,55, "Gelber Sack", "fonts/calibrib30",1] },{"text":[171,55, "In 5 Tagen", "fonts/bahnschrift30",1] }]"
sascha_hemi added the bug label 2026-03-20 21:06:56 +01:00
Author
Owner

@nlimper commented on GitHub (Feb 28, 2025):

The AP is out of memory. Possible causes: the resolution of the tag is too big (but if a see the coordinates in the json content, it's just a small tag), or maybe there are several tags having pending data (are you updating multiple tags at a time?).

What kind of AP do you use?
Can you copy/past the status bar of the web interface? (free heap: 184.03 kB ┇ free PSRAM: 7.63 MB ┇ db size: 5.71 kB ┇ db record count: 29 ┇ filesystem free: 5.37 MB ┇ uptime: 12h 35m 54s)

<!-- gh-comment-id:2690957021 --> @nlimper commented on GitHub (Feb 28, 2025): The AP is out of memory. Possible causes: the resolution of the tag is too big (but if a see the coordinates in the json content, it's just a small tag), or maybe there are several tags having pending data (are you updating multiple tags at a time?). What kind of AP do you use? Can you copy/past the status bar of the web interface? (`free heap: 184.03 kB ┇ free PSRAM: 7.63 MB ┇ db size: 5.71 kB ┇ db record count: 29 ┇ filesystem free: 5.37 MB ┇ uptime: 12h 35m 54s`)
Author
Owner

@gitpower2017 commented on GitHub (Feb 28, 2025):

It is only updated one day at a time.

current env: OpenEPaperLink_Mini_AP_v4
build date: 2024-12-08 21:06
esp32 version: 2.75
filesystem version: 2.75
psram size: 8382631
flash size: 16777216

However, the oepAP has rebooted.
free heap: 176.30 kB ┇ free PSRAM: 7.96 MB ┇ db size: 2.72 kB ┇ db record count: 17 ┇ filesystem free: 4.53 MB ┇ uptime: 42m 9s

<!-- gh-comment-id:2691002003 --> @gitpower2017 commented on GitHub (Feb 28, 2025): It is only updated one day at a time. current env: OpenEPaperLink_Mini_AP_v4 build date: 2024-12-08 21:06 esp32 version: 2.75 filesystem version: 2.75 psram size: 8382631 flash size: 16777216 -------------------------- However, the oepAP has rebooted. free heap: 176.30 kB ┇ free PSRAM: 7.96 MB ┇ db size: 2.72 kB ┇ db record count: 17 ┇ filesystem free: 4.53 MB ┇ uptime: 42m 9s
Author
Owner

@nlimper commented on GitHub (Feb 28, 2025):

it's not about that particular tag, but about all tags connected to the AP: are multiple updated at once?
Anyway: does it work again now the AP has rebooted? Or does it never work with that tag?

<!-- gh-comment-id:2691095665 --> @nlimper commented on GitHub (Feb 28, 2025): it's not about that particular tag, but about all tags connected to the AP: are multiple updated at once? Anyway: does it work again now the AP has rebooted? Or does it never work with that tag?
Author
Owner

@gitpower2017 commented on GitHub (Feb 28, 2025):

I'm not 100% sure, usually only one is updated at a time and not all at the same time.
After the restart all tags work again.
I have now activated the daily reboot.

<!-- gh-comment-id:2691324653 --> @gitpower2017 commented on GitHub (Feb 28, 2025): I'm not 100% sure, usually only one is updated at a time and not all at the same time. After the restart all tags work again. I have now activated the daily reboot.
Author
Owner

@nlimper commented on GitHub (Feb 28, 2025):

In that case it is to be expected, due to memory fragmentation, the daily reboot is useful to enable (as it is by default).

<!-- gh-comment-id:2691368233 --> @nlimper commented on GitHub (Feb 28, 2025): In that case it is to be expected, due to memory fragmentation, the daily reboot is useful to enable (as it is by default).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/OpenEPaperLink#2479