Closed TheStork239 closed 3 years ago
last failed alloc call: 4020F4F5(24)
your device is running out of memory - this could be because your last config was just close to the limit, and changes in 1.19 just bumped it over the edge.
It may help to go into the fonts
glyphs (for example in Roboto-bold) and manually enabled just the glyphs you really need (the default is the whole ASCII latin set, so quite a few characters).
Thanks @OttoWinter, I think you are right. I reduced the number of fonts / glyphs and that got it working again. Interestingly it wasn't shown as high RAM usage at time of compiling, and the fact that it had worked with a previous ESPHome version really threw me, as I incorrectly assumed it was not my code causing it.
Operating environment/Installation (Hass.io/Docker/pip/etc.):
Hass.io
ESP (ESP32/ESP8266, Board/Sonoff):
ESP8266, Wemos D1 Mini
ESPHome version (latest production, beta, dev branch)
1.19.2 (issue started after upgrading from 1.18, worked fine there)
Affected component:
Waveshare e-ink display https://esphome.io/components/display/waveshare_epaper.html
Description of problem: The code for my waveshare 4.2in e-ink display worked perfectly in ESPHome 1.18, but after upgrading to 1.19.1 and 1.19.2 the same yaml configuration causes the ESP to either reset (sometimes repeatedly) or become unresponsive to Home Assistant. Quite often the ESP will fetch only one of the HA sensor values to be displayed, and become unresponsive after that, as is the case in the example log file below. (In 1.18 it fetches and displays values from several different sensors and updates them on the display every 600 seconds).
I have the previous bin file created in 1.18, and have tried compiling the same yaml configuration in 1.19.2 (and before then in 1.19.1). The bin file compiled with the 1.19.x versions have this issue, while the bin file created with 1.18 using the same yaml config file works fine without any resets or becoming unresponsive.
Problem-relevant YAML-configuration entries:
Logs (if applicable):
Additional information and things you've tried: The bin file created in 1.18 works fine, while the same yaml configuration compiled in 1.19.2 (and before then in 1.19.1) have this issue of resets and broken fetching of sensor data.