LVGL 9 doesn't use LV_MEM_CUSTOM or LV_ENABLE_GC (BSP-714)

[mattmatt206]

Board

ESP32S3-WROOM1-N16R8 Custom Board

Hardware Description

LCD RGB565 480x854

IDE Name

VSCode

Operating System

Windows 11

Description

in /lvgl9/esp_lvgl_port.c
function lvgl_port_task_deinit

lv_deinit is only called for the following
#if LV_ENABLE_GC || !LV_MEM_CUSTOM

Neither of which is in LVGL9

I think it should be
#if LV_USE_STDLIB_MALLOC == LV_STDLIB_BUILTIN

Sketch

esp_err_t test_dev_lcd_lvgl_deinit(void)
{
    esp_err_t ret = ESP_OK;

    // Remove display from LVGL
    if (disp != NULL) {
        ret = lvgl_port_remove_disp(disp);
        ESP_RETURN_ON_ERROR(ret, TAG, "Failed to remove display from LVGL");
        disp = NULL;
    }

    ESP_ERROR_CHECK(esp_lcd_panel_del(panel_handle));
    panel_handle = NULL;

    // Deinitialize LVGL port
    ret = lvgl_port_deinit();
    ESP_RETURN_ON_ERROR(ret, TAG, "Failed to deinitialize LVGL port");

    return ESP_OK;
}

void deinit()
{
    ESP_ERROR_CHECK(lvgl_port_stop());
    vTaskDelay(pdMS_TO_TICKS(100));
    ESP_ERROR_CHECK(test_dev_lcd_lvgl_deinit());
}

Other Steps to Reproduce

No response

I have checked existing issues, README.md and ESP32 Forum

• I confirm I have checked existing issues, online documentation and Troubleshooting guide.

[github-actions]

Hi @mattmatt206! Please be aware that (1) the following suggestions are generated by a bot and haven't been fact-checked by Espressif Systems, (2) burning eFuses and enabling security features are irreversible operations and can damage your ESP32 device. We hope that this message will help you until an Espressif Engineer looks at your issue.

---

Thanks for reporting this. You’re right about the condition being outdated for LVGL v9.

In LVGL v9, the legacy macros LV_MEM_CUSTOM and LV_ENABLE_GC are no longer used. The lvgl port should gate lv_deinit() based on the stdlib backend configuration. Using LV_USE_STDLIB_MALLOC == LV_STDLIB_BUILTIN matches LVGL v9’s memory config model and is consistent with the esp_lvgl_port’s stated LVGL9 support and ongoing updates. [LVGL comp; esp_lvgl_port changelog]

Proposed fix in esp_lvgl_port.c (lvgl_port_task_deinit):

• Replace:
  • #if LV_ENABLE_GC || !LV_MEM_CUSTOM
• With:
  • #if LV_USE_STDLIB_MALLOC == LV_STDLIB_BUILTIN

This aligns the deinit path with LVGL v9’s allocation selection while keeping behavior correct across LVGL8/9 per the compatibility notes in esp_lvgl_port. [esp_lvgl_port readme; esp_lvgl_port changelog]

If you’re on esp_lvgl_port ≥2.3 (LVGL9 supported), this change should be safe. If you use LVGL8 via the compatibility layer, ensure the condition remains valid for that configuration too (the port supports both and retypes some symbols). [esp_lvgl_port readme]

Note: I don’t see this exact patch already mentioned in the public changelog, so it may require a PR to esp_lvgl_port. [esp_lvgl_port changelog]