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

13 custom fields renders 4/10 times on ESP8266 #1787

Open
F1p opened this issue Dec 24, 2024 · 3 comments
Open

13 custom fields renders 4/10 times on ESP8266 #1787

F1p opened this issue Dec 24, 2024 · 3 comments

Comments

@F1p
Copy link

F1p commented Dec 24, 2024

I have a reasonable sized project, running 13 custom fields and have an issue on the ESP8266 where 4/10 times the custom fields render blank on refresh (as per screenshots) but issue doesn't seem to impact the ESP32. Any idea's why this might happen?

Screenshot 2024-12-19 133629
Screenshot 2024-12-19 134342

Running the latest master branch,

ESP8266 running
Core version
3.1.2
Boot version
31
CPU frequency
160MHz
Memory - Free heap
12912 bytes available
Memory - Sketch size
Used / Total bytes
489296 / 3143504

@F1p
Copy link
Author

F1p commented Dec 29, 2024

Might be an issue improved by adjusting MMU to 16KB Cache + 48K IRAM instead of balanced (32/32K)

@tablatronix
Copy link
Collaborator

Its probably memory, the html is output as a string on the stack, If you are using alot of params this can be optimized by using chunked outputting and allocated buffers, I think there is an issue here to start looking into it..

#1319
#518

@F1p
Copy link
Author

F1p commented Dec 30, 2024

Its probably memory, the html is output as a string on the stack, If you are using alot of params this can be optimized by using chunked outputting and allocated buffers, I think there is an issue here to start looking into it..

#1319 #518

Thanks, will try chunked response for now

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